Two Laptop Bag*
The moose likes Websphere and the fly likes Hung threads in WAS5.1 logs Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "Hung threads in WAS5.1 logs" Watch "Hung threads in WAS5.1 logs" New topic
Author

Hung threads in WAS5.1 logs

saida reddy
Greenhorn

Joined: Mar 21, 2006
Posts: 1
Hi All,

I am facing a issue with WAS5.1 server .In our server logs we are getting following thread hung warning messages frequently.so server performance getting degraded.can any one please any point to solve this.

3/17/06 7:47:30:566 EST] 38305b ThreadMonitor W WSVR0605W: Thread "Servlet.Engine.Transports : 53" (199a51e) has been active for
607,873 milliseconds and may be hung. There are 1 threads in total in the server that may be hung.
[3/17/06 7:47:30:574 EST] 38305b ThreadMonitor W WSVR0605W: Thread "Servlet.Engine.Transports : 50" (1792081) has been active for
613,849 milliseconds and may be hung. There are 2 threads in total in the server that may be hung.
[3/17/06 7:47:30:579 EST] 38305b ThreadMonitor W WSVR0605W: Thread "Servlet.Engine.Transports : 31" (2893ce) has been active for 7
74,382 milliseconds and may be hung. There are 3 threads in total in the server that may be hung.
[3/17/06 7:47:30:584 EST] 38305b ThreadMonitor W WSVR0605W: Thread "Servlet.Engine.Transports : 8" (26a725) has been active for 77
4,561 milliseconds and may be hung. There are 4 threads in total in the server that may be hung.
[3/17/06 7:47:30:589 EST] 38305b ThreadMonitor W WSVR0605W: Thread "Servlet.Engine.Transports : 25" (1662529) has been active for
774,383 milliseconds and may be hung. There are 5 threads in total in the server that may be hung.
[3/17/06 7:47:30:594 EST] 38305b ThreadMonitor W WSVR0605W: Thread "Servlet.Engine.Transports : 49" (1106993) has been active for
632,845 milliseconds and may be hung. There are 6 threads in total in the server that may be hung.

Thanks
saidareddy
Pat Flickner
Ranch Hand

Joined: Nov 17, 2003
Posts: 173
This can be happening for any number of reasons, but one of the primary things that I've come across is that a connection pool may be staying open because the query or stored procedure the application sent isn't being resolved but the database thinks it should be. You should have logs of the items that are being accessed. Hopefully you have a development enviornment in which you can restart the server and test one application at a time. Go ahead and beat the heck out of an application, then wait about 6 minutes or so and then see if there's a log entry like the ones you're getting now. Once you get an offending application, go to your WSAD and start your server in debug mode and run it through until you get hung. Note the query, stored procedure, whatever, and then contact whoemver is responsible for it to find out why it's not working correctly so you can get it fixed. Once the one is fixed, repeat for each application until you clean up everything. Good luck.
Brian Hennessy
Ranch Hand

Joined: Oct 24, 2005
Posts: 57
Hi
Hung threads are horrible.
I suppose the best place to start is to see if a javacoredump has been initiated by the appserver .The file will be called something like javacore528596.1138290747.txt. The output of this javacore can be analyzed by IBM thread analyzer tool, you can get it off the IBM site. In here you can see all sorts of wonderful things such as the method that is executed by the majority of your threads,lock etc. On the threadanalyzer site there is some guide to interpreting the javacoredump.

If there is no core dump you can initiate a ps kill -11 I think on the app server process and this will force a javacoredump.

Depending on the outcome of this you may find something that stands out you can fix in your app or will at least guide you if you need to enabling tracing etc on a server to pin point the problem. Also check the WAS defect list for the version you're running and see if anything stands out particularly after you run the analysis on your threads.

http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg27006879

Sorry I can't be of more help and good luck with this I know how much of a pain they can be to resolve


 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Hung threads in WAS5.1 logs