Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Invalid
-
2.6.0
-
None
-
None
-
Windows 2K3EE
Websphere 6.1.0.9 - JVM 1.5 - Info below:IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows Server 2003 x86-32 j9vmwi3223-20060504 (JIT enabled)
J9VM - 20060501_06428_lHdSMR
JIT - 20060428_1800_r8
GC - 20060501_AA)
JCL - 20060511aJSPWiki is deployed with a basic config file (no container/authentication/jaas/web.xml related customizations).
Windows 2K3EE Websphere 6.1.0.9 - JVM 1.5 - Info below: IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows Server 2003 x86-32 j9vmwi3223-20060504 (JIT enabled) J9VM - 20060501_06428_lHdSMR JIT - 20060428_1800_r8 GC - 20060501_AA) JCL - 20060511a JSPWiki is deployed with a basic config file (no container/authentication/jaas/web.xml related customizations).
Description
Clicking on the 'Info' tab of any page causes the java.exe process running Websphere to spike to 100% in CPU usage permanently.
I have tried to create a JVM thead dump however due to the nature of all the CPU being consumed, the signal to generate a thread dump does not get detected. If only Windows had a kill -QUIT pid command.
I wish I had some more information. I'm not aware of any sort of tracing I could turn on in JSPWiki, please let me know if there is anything else I can help with information wise.
Apart from this, Kudos on 2.6.0 (cvs), the latest release is looking/performing very nicely.