IBM WebSphere - Consuming 99% CPU

[Ravi Bhavaraju]

OS: Windows NT
Software: IBM WebSphere
Problems:
1. IBM WebSphere Server when started (java.exe) takes 99% CPU.
2. Even when the Server is stopped, java.exe keeps on runing and
consumes 99% CPU
IBM sugessted a Fix Pack for this, even after applying also, problem persists
Suggest needful

[L Goundalkar]

Hi Ravi,
The minimum requirement for WS v 3.5 is 250 MB RAM and preferred is 500MB RAM.
So naturally it will occupy the most space in memory.
about the bug, I am not sure. for me it works fine. I have v3.5.
Thanks.

------------------
L Goundalkar
[e-mail]
Sun Certified Programmer for Java 2 Platform

[James Swan]

Not an answer to your question, but I have had the same problems with WebSphere 3.5 on Windows 2000.
Workstation:
Windows 2000, PIII 600 MHz, 256MB ram etc with WAS 3.5, the WAS service worked fine for a while, and then started consuming 99% cpu.
After numerous reinstalls of WAS, the solution I took was to switch to Red Hat Linux 7.0 and WAS Advanced Edition 3.5 for Linux.
James.

[Ravi Bhavaraju]

Hi,
Sorry for not mentioning my machine config .. it's 512 MB RAM.
Even than it's occupying the maximum CPU.
Thanks for Response ..
Ravi

Originally posted by L Goundalkar:
Hi Ravi,
The minimum requirement for WS v 3.5 is 250 MB RAM and preferred is 500MB RAM.
So naturally it will occupy the most space in memory.
about the bug, I am not sure. for me it works fine. I have v3.5.
Thanks.

[Ravi Bhavaraju]

Hi James,
When ever we try to access the Web Application from localhost ie from the machine where WebSephere exists, this problem hits.
Applying the Fix-Pack provided by IBM and changing some config files solved in one of machines which we are using for Production.
But the same when applied for other machine which will are using for development doesn't.
It's Strange ..
Thanks for your reponse and be back when I solve it..
Ravi

Originally posted by james swan:
Not an answer to your question, but I have had the same problems with WebSphere 3.5 on Windows 2000.
Workstation:
Windows 2000, PIII 600 MHz, 256MB ram etc with WAS 3.5, the WAS service worked fine for a while, and then started consuming 99% cpu.
After numerous reinstalls of WAS, the solution I took was to switch to Red Hat Linux 7.0 and WAS Advanced Edition 3.5 for Linux.
James.

[Huiming Gu]

I have the same problem on WIN2000 1G-CPU 512RAM.

I think there is something wrong with the JVM. It only happend when installed sun JDK1.3. What I did is:

Rebuild build the machine and install WAS4.0.

Never happen again, even though this is the worst solution I can think of.

[Tony Chen]

Originally posted by Ravi Bhavaraju:
OS: Windows NT
Software: IBM WebSphere
Problems:
1. IBM WebSphere Server when started (java.exe) takes 99% CPU.
2. Even when the Server is stopped, java.exe keeps on runing and
consumes 99% CPU
IBM sugessted a Fix Pack for this, even after applying also, problem persists
Suggest needful

I've seen this problem before. Are you running WAS 3.5 Std.Ed. with InstantDB? If so, then InstantDB is the trouble-maker!
Solution: Switch from InstantDB to DB2 or Oracle.
------------------
Tony Chen
SCJP, ICS & ICSD (WebSphere)

[Tom Greisinger]

Try to upgrade to WebSphere 3.5.4.
That should fix that bug.
Tom

[Gene Smith]

Tony Chen is right. If you are using WebSphere Standard version, it ships with InstantDB which it uses for its administration database. InstantDB is flaky, it might work on most machines but can definitely cause the java.exe process to eat up the processor on some other machines. I had the same problem for weeks. I finally used IBM's migration tool to migrate WebSphere from InstantDB to MS-SQL Server as the admin database. MS-SQL was on the same box and being used for the application so why not let WebSphere use it too. Ever since the migration away from InstantDB the java.exe process has never hogged the CPU.