Support Article

Stuck Requestors using CPU

SA-32649

Summary



CPU consumption is elevated for production JVMs. Upon investigating, evidence of long running (stuck) requestors force restart of the JVM in order to resolve.

Error Messages



"WebContainer : 49" Id=81791 in RUNNABLE
BlockedCount : 24, BlockedTime : -1, WaitedCount : 91971, WaitedTime : -1
at java.util.HashMap.findNonNullKeyEntry(HashMap.java:605)
at java.util.HashMap.putImpl(HashMap.java:701)
at java.util.HashMap.put(HashMap.java:684)
at com.pegarules.generated.xml.ra_action_pyanyns_pyanyname_d53058bf5b6058138ce979392b037ae8.typeSubstitutionHelper_15
(ra_action_pyanyns_pyanyname_d53058bf5b6058138ce979392b037ae8.java:409)
at com.pegarules.generated.xml.ra_action_pyanyns_pyanyname_d53058bf5b6058138ce979392b037ae8.typeSubstitutionHelper_16
(ra_action_pyanyns_pyanyname_d53058bf5b6058138ce979392b037ae8.java:414)


Steps to Reproduce



Observe the CPU usage and requestors.

Root Cause



A defect in Pegasystems' code or rules results in repeated use of HashMap.

Resolution



Apply HFix-31258.

Published January 19, 2017 - Updated February 24, 2017

Have a question? Get answers now.

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