Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Hung threads observed and application was non responsive

SA-20784

Summary



Users were unable to access the PRPC instance and the application was non-responsive. In the log files, few hung threads were observed.

Error Messages



[3/8/16 4:24:13:195 EST] 00000035 ThreadMonitor W   WSVR0605W: Thread "WebContainer : 39" (00008467) has been active for 718138 milliseconds and may be hung.  There is/are 39 thread(s) in total in the server that may be hung.
                at com.pega.apache.log4j.Category.callAppenders(Category.java:204)
                at com.pega.pegarules.priv.LogHelper.infoForced(LogHelper.java:1142)


Steps to Reproduce



1. Enable AES on the PRPC instance
2. Disabled the AES partially (stop the monitoring AES node and do not comment out the setting in the prlogging)
3. Start seeing the hung threads and PRPC instance becomes non responsive


Root Cause



The AES configurations was disabled partially on the monitored node. As per the log traces, the stuck or hung threads while looking for the AES end point URL referenced in the prlogging.xml file.

Resolution



The AES specific settings were disabled from the PRPC monitored node.

Suggest Edit

Published March 16, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us