This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Hello All,
Since there was a database server migration,We have been seeing this issue frequently and this is bringing the Maximo application down.
We are on Maximo version 7.5.0.5,Websphere 7.0.0.15,Oracle 11g
I have checked that the VMS on which the Maximo is hosted are having enough memory(16GB RAM),enough disk space and also the websphere application server is configured as per the IBM recommendation pertaining to thread pool,web container settings.
I am unable to get any clue leading to the root cause of the problem.I even tried doing the installation of websphere on a fresh Virtual machine,but still the issue persists. We have taken the network trace,generated heap dumps and the database logs also provide no information leading to the cause of the problem.
Could this be related purely on the database side???Please help and suggest.
[8/3/16 14:24:16:431 GST] 00000003 ThreadMonitor W WSVR0605W: Thread "WebContainer : 38" (000002e0) has been active for 771101 milliseconds and may be hung. There is/are 42 thread(s) in total in the server that may be hung. at org.apache.log4j.Category.callAppenders(Category.java:204) at org.apache.log4j.Category.forcedLog(Category.java:391) at org.apache.log4j.Category.log(Category.java:856) at psdi.util.logging.Log4jLogger.debug(Log4jLogger.java:81) <etc>
Did you check this? Thread "WebContainer : 0" (00000029) has been active for 647279 milliseconds and may be hung http://stackoverflow.com/questions/27042528/thread-webcontainer-0-00000029-has-been-active-for-647279-milliseconds-and
http://stackoverflow.com/questions/27042528/thread-webcontainer-0-00000029-has-been-active-for-647279-milliseconds-and
Thread "WebContainer : 0" (00000029) has been ... http://stackoverflow.com/questions/27042528/thread-webcontainer-0-00000029-has-been-active-for-647279-milliseconds-and I am getting the following exception in WebSphere while trying to generate an excel report using jasper. ThreadMonitor W WSVR0605W: Thread "WebContainer...
View on stackoverflow.com http://stackoverflow.com/questions/27042528/thread-webcontainer-0-00000029-has-been-active-for-647279-milliseconds-and
Preview by Yahoo
Seems like checking the SystemOut.log and seeing what modules people are using and/or reports running may be helpful.
Is there a pattern such as time of day, day of week, etc that the hang occurs?
Hi,
I checked this tech note,but already the settings on the websphere are as per the IBM recommendation,Would I be required to modify the parameters as even after I followed the same guidelines,I was getting the thread hanging error.
Regards,
Mahadevan
Dear Experts,
Could you please help me with your suggestions for this problem.
We faced the thread hanging issue immediately after the database server was moved to a new data center.Earlier the application server and database server were in same data center.
The heap dump was generated when the issue occurred and could not find any connection leak issue from the application side.
Also,the IBM recommendation for adding custom properties to set the thread hang alarm to false didnt work as the logs were not getting generated after doing the setting and the response still was coming as HTTP Error 500.
Is the only solution for this issue is keep the application and database servers in the same data center?Please help