Support Article
System hangs or freezes due to hung threads
SA-31329
Summary
One of the production systems went into a hung state. Many hung thread warning messages are observable in the WebSphere SystemOut logfile.
Error Messages
11/19/16 0:02:40:835 EST] 000000aa ThreadMonitor W WSVR0605W: Thread "WorkManager.PegaWorkManager : 16" (0000058b) has been active for 609045 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung.
at com.pega.pegarules.bootstrap.loader.PRAppLoader.loadClass(PRAppLoader.java:649)
Steps to Reproduce
Unknown
Root Cause
A defect or configuration issue in the operating environment.
A database job was causing significant latency on the database server. This had the effect of making the interactions between the Pega and the database slow to the point of unusability.
Resolution
Make the following change to the operating environment: The database job was canceled, thus eliminating the issue.
Published December 14, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.