Hung threads observed and application was non responsive
Users were unable to access the PRPC instance and the application was non-responsive. In the log files, few hung threads were observed.
[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.
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
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.
The AES specific settings were disabled from the PRPC monitored node.