wood burning stoves 2.0*
The moose likes Websphere and the fly likes HELP!  Websphere ThreadMonitor Exception Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Products » Websphere
Bookmark "HELP!  Websphere ThreadMonitor Exception " Watch "HELP!  Websphere ThreadMonitor Exception " New topic
Author

HELP! Websphere ThreadMonitor Exception

Andres Delrotti
Ranch Hand

Joined: Aug 11, 2005
Posts: 137
I deployed an application in the Websphere server. When I tried to log in, I noticed that it was very slow (it took about ten minutes), both in integration and production Websphere servers that we use. There wasn�t any significant change in memory usage in the integration server after the login process. I looked at the SystemOut log and found this:



[6/15/06 11:42:44:445 CDT] 1d2b8ac4 PropertyMessa I org.apache.struts.util.PropertyMessageResources Initializing, config='org.apache.struts.taglib.html.LocalStrings', returnNull=true

[6/15/06 11:55:42:908 CDT] 40598ac4 ThreadMonitor W WSVR0605W: Thread "Servlet.Engine.Transports : 1" (72020ac5) has been active for 738,559 milliseconds and may be hung. There are 1 threads in total in the server that may be hung.

[6/15/06 11:55:42:964 CDT] 40598ac4 ThreadMonitor W WSVR0605W: Thread "Servlet.Engine.Transports : 0" (1c0c4ac4) has been active for 699,515 milliseconds and may be hung. There are 2 threads in total in the server that may be hung.

[6/15/06 12:02:39:728 CDT] 72020ac5 WebGroup I SRVE0180I: [HCC.war] [/HCC] [Servlet.LOG]: /jsp/ess_quickview.jsp: init

[6/15/06 12:02:51:960 CDT] 72020ac5 ThreadMonitor W WSVR0606W: Thread "Servlet.Engine.Transports : 1" (72020ac5) was previously reported to be hung but has completed. It was active for approximately 1,167,612 milliseconds. There are 1 threads in total in the server that still may be hung.

[6/15/06 12:07:58:555 CDT] 1c0c4ac4 ThreadMonitor W WSVR0606W: Thread "Servlet.Engine.Transports : 0" (1c0c4ac4) was previously reported to be hung but has completed. It was active for approximately 1,435,163 milliseconds. There are 0 threads in total in the server that still may be hung.

[6/15/06 12:34:43:182 CDT] 12004ac4 ThreadMonitor W WSVR0605W: Thread "Servlet.Engine.Transports : 1" (72020ac5) has been active for 711,318 milliseconds and may be hung. There are 1 threads in total in the server that may be hung.

[6/15/06 12:42:25:152 CDT] 72020ac5 ThreadMonitor W WSVR0606W: Thread "Servlet.Engine.Transports : 1" (72020ac5) was previously reported to be hung but has completed. It was active for approximately 1,173,288 milliseconds. There are 0 threads in total in the server that still may be hung.

[6/15/06 13:07:43:316 CDT] 40598ac4 ThreadMonitor W WSVR0605W: Thread "Servlet.Engine.Transports : 2" (1d2b8ac4) has been active for 624,834 milliseconds and may be hung. There are 1 threads in total in the server that may be hung.


Also, I was the only one who was using the integration server at that time so I�m sure that these messages were generated through the application I was using. Can you guys take a look at and see if these messages can be fatal or may later cause huge memory usage? and what is really the main cause for this exception? I�m also concerned about the slow response time overall for the application, both in integration and production. Just tell me if you need to take a look at some portions of the application's source codes.


Any form of HELP would be appreciated. Thanks.

I really hope you guys could help me on this. I need to solve this problem URGENT!
vishwa venkat
Ranch Hand

Joined: Nov 22, 2003
Posts: 185
refer to this-

http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1//index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/ctrb_hangdetection.html
 
GeeCON Prague 2014
 
subject: HELP! Websphere ThreadMonitor Exception