2. Hang
2-1. Phenomenon
You can not get any response from your application even the process is still alive.
(Check it with ps command)
I have experienced with such a case:
1) There is contact came from customer that they have submitted form in somehow a function but got no response back from the WebSphere Application Server even have been waiting for long time.
2) Continuously, similar contact came from other place said that even login process can not be finished for a long time.
3) Customer mat see the following error in the SystemOut.log of WebSphere:
[ 06/07/05 13:31:52:601 JST] 14875e8 ThreadMonitor W WSVR0605W : Thread
"Servlet.Engine.Transports : 350" (2333b4c6
0) has been active for 721,162 milliseconds and may be hung. There are
1 threads in total in the server that may be hung.
:
:
[ 06/07/05 13:40:52:995 JST] 14875e8 ThreadMonitor W WSVR0605W : Thread
"Servlet.Engine.Transports : 560" (386d34c6
0) has been active for 612,670 milliseconds and may be hung. There are
50 threads in total in the server that may be hung.
Here by seeing the last message we got to know 50 Threads have already been hung, and 50 is the number of threads we have defined to the running WebSphere Application Server, which means there is not thread can be available to response to user’s request.
We can not get any other information for the problem except for those I have outlined above, as in most of the case you can not found error information like any exception being thrown in hung problem.
4)
2-2. Handling
So with the limited information how can we resolve the problem? We should know firstly how hang can get happened.
The following reasons can be considered when you get into such a situation:
1) Bug in your application or module of third party
l Deadlock
l Indefinite Loop : could make JVM down with a StackOverflow error
l R