Wildfired.exe taking up all of the available CPU usage

Kurt1 · January 2, 2007, 4:07pm

Wildfired.exe is maxing out the CPU usage to 100% making the server virtually useless to work on. It seems to be taking any all available resources for its self. Any suggestion on how to limit the resources that Wildfire uses will be greatly appreciated.

Running Windows 2000 Advance Server

Wildfire 3.1.1

Environment

JVM Version and Vendor: 1.5.0_08 Sun Microsystems Inc. – Java HotSpot™ Server VM

Appserver: Jetty/5.1.x

OS / Hardware: Windows 2000 / x86

Locale / Timezone: en / Eastern Standard Time (-5 GMT)

Java Memory

25.87 MB of 63.31 MB (40.9%) used

Thanks for the help!

Message was edited by: mathiakk

More Info. The CPU gets maxed out as soon as Wildfire starts. A filed called admin-console.log gets created and is at 0 bytes. The server runs with a maxed out CPU till something is dumped to the admin-console.log file, some times as much as 3 GB worht of data, and then the CPU usage drops down to normal. I am not sure what is in this .log file because I do not have a word processor/text editor that will open that large of a file. Does any know of a text editor that will open a file this large?? Or does anyone know what might be the cause of this problem??

Thanks for the help.

Message was edited by: mathiakk

More Info. The CPU gets maxed out as soon as Wildfire starts. A filed called admin-console.log gets created and is at 0 bytes. The server runs with a maxed out CPU till something is dumped to the admin-console.log file, some times as much as 3 GB worht of data, and then the CPU usage drops down to normal. I am not sure what is in this .log file because I do not have a word processor/text editor that will open that large of a file. Does any know of a text editor that will open a file this large?? Or does anyone know what might be the cause of this problem??

Thanks for the help.

LG1 · January 2, 2007, 8:36pm

Hi,

which database are you using and are you using AD?

Did you install any plugins?

Do you see errors in the log files?

LG

Kurt1 · January 2, 2007, 9:27pm

Thanks for the responce!!!

Database being used - Microsoft SQL Server 08.00.0760 which is on a different server the Wildfire

Database Name - wildfire

I checked the log files and very little mentioned or entered with todays date. The one log file that concerns me a great deal is the Admin-Console.log file. It is up to 3 GB just sense this morning. I have not installed any Plug-ins.

When I installed Wildfire I pretty much took the defaults, didn’'t really have any troubles setting up Active Directory/LDAP.

There is an entry in the Error log that I am wondering about, again, dated back on 12/15/2006

2006.12.15 09:03:08 org.jivesoftware.wildfire.server.OutgoingServerSession.createOutgoingSession(Out goingServerSession.java:339) Error creating secured outgoing session to remote server: (our domain name is listed after that)

java.net.SocketTimeoutException: Read timed out

at java.net.SocketInputStream.socketRead0(Native Method)

at java.net.SocketInputStream.read(Unknown Source)

at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(Unknown Source)

at sun.nio.cs.StreamDecoder$CharsetSD.implRead(Unknown Source)

at sun.nio.cs.StreamDecoder.read(Unknown Source)

at java.io.InputStreamReader.read(Unknown Source)

at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:2992)

at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)

at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410)

at org.jivesoftware.wildfire.net.MXParser.nextImpl(MXParser.java:331)

at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)

at org.jivesoftware.wildfire.server.OutgoingServerSession.createOutgoingSession(Ou tgoingServerSession.java:288)

at org.jivesoftware.wildfire.server.OutgoingServerSession.authenticateDomain(Outgo ingServerSession.java:140)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise.createSessionAndSendPac ket(OutgoingSessionPromise.java:130)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise.access$300(OutgoingSess ionPromise.java:40)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise$1$1.run(OutgoingSession Promise.java:95)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

This file is about 200K in size.

If there is anything else that you need let me know!! Any specific files you would like me to look at or look for?

Thanks again

Kurt

LG1 · January 2, 2007, 10:31pm

Hi,

maybe you can use StackTrace to get a stack trace of Wildfire while it is using 100% cpu.

It may help to use the Task Manager to set Wildfire’'s priority to low if this is possible for a Windows Service.

Does it use 100% CPU all the time or only if specific actions do occur?

LG

Kurt1 · January 3, 2007, 5:45pm

It its 100% as soon as I launch wildfire. I may have some helpful information on this Admin-Counsole.log file. Here is a very small part of that file.

6:56:57.630 WARN!! [Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=9091]]] org.mortbay.util.ThreadedServer.acceptSocket(ThreadedServer.java:461) >02> EXCEPTION

javax.net.ssl.SSLException: No available certificate or key corresponds to the SSL cipher suites which are enabled.

at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.checkEnabledSuites(Unknown Source)

at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(Unknown Source)

at org.mortbay.util.ThreadedServer.acceptSocket(ThreadedServer.java:432)