CLMHelp crashing Websphere
![]()
Chris Ryan (157●3●24●28)
| asked Jun 20 '13, 1:39 p.m.
retagged Jun 21 '13, 1:27 p.m. by Amy Laird (165●1●4)
When I attempt to visit https://127.0.0.1:9443/clmhelp/updater/updatewar.jsp in my attempt to enable local help (and disable the internet help), the page hangs.
I view my SystemOut.log, and there is lines such as WSVR0605W: Thread "WebContainer : 12" has been active for 692205 milliseconds and may be hung. There is/are 5 thread(s) in total in the server that may be hung. And then my server crashes shortly after. Has anyone else seen this?
showing 5 of 7
show 2 more comments
|
3 answers
![]()
Hi Chris,
Just to eliminate any type of resource contention, I would: 1. Increase the thread pool to min=max=500. NOTE: Seting it this high is to remove any dout that there is an issue with the thread pool being too low. 2. Increase the java heap to min=max=4gig 3. Also to eliminate this is an issue with connectivity, ensure that there is a stable connection to the internet. Attempt to reproduce the issue. If it persists 1. Capture WAS logs, jts/ccm logs and java cores 2. View the PMI data to determine if the thread pool was exhausted 3.Open a service request against WebSphere. This way we can have the WAS java team review the WAS logs and java cores. If needed they will pass the PMR over to the CLM support team. 4. Also reference this forum post in the PMR. |
Comments
Hi Chris, that is odd - I haven't seen anything like that before. Assuming the about page loads, can you tell me what version of the help system are you using (can be found at https://127.0.0.1:9443/clmhelp/about/about.jsp)
Thanks for the response, Chris.
The help version I'm using is as follows:
Eclipse Version: 3.7.0v20110613
Version: M4.2012
WAR Type: UA Delivery WAR
...
...
And yes, the page loaded. :)
hi Chris,
What do you mean by crashing? Is the server process running and the server is not accessible? Or there is no server process running?
The server process eventually becomes unusable, cannot be shut down using the stopServer script, and must be killed manually. i.e. kill -9 <process ID>
Ouch. So updatewar.jsp is causing the webserver process to hang. The only thing I can think of is maybe some javascript function is caught in an endless loop. Its possible you could see where the error happens using firebug or some similar tool, but that would be a pain. We might be able to get you a newer version of the WAR to try (M2.2013 is the latest at the moment) - let me look into that.
Chris, have you had any luck looking into it?
I just attempted to stop the clmhelp application, and that action produced 10 hung threads. I've had no choice but to kill my production WAS process, restart, and then uninstall the CLMHelp application as it's ununsable. Unfortunately.
Any suggestions would be fantastic.