Memory space manipulating in Java(Section four:Problems Resolving - part two)

最新推荐文章于 2021-08-23 09:24:36 发布

tangbomaozero

最新推荐文章于 2021-08-23 09:24:36 发布

阅读量2.4k

点赞数

分类专栏： Java Basic 文章标签： java thread websphere workflow application server

本文链接：https://blog.csdn.net/tangbomaozero/article/details/1451460

版权

本文讨论了Java应用程序挂起的现象和处理方法，包括无响应的原因分析，如死锁、无限循环、后台资源等待及性能下降等。通过案例分析了MQ Workflow导致的挂起情况，并提供了排查思路。

摘要由CSDN通过智能技术生成

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.