Support Article
Hung JVM threads and the database connection pool maxed out
SA-54447
Summary
JVM threads hang on one node of the server causing the database connection Pool to max out.
This occurs with the PRRuntimeError post which the server threads proceed to the TIMED_WAITING stage. The JDBC Connection pool usage increases to 100% on this node and the connections are not released until restart.
Error Messages
pega.pegarules.pub.PRRuntimeError com.pega.pegarules.pub.PRRuntimeError: PRRuntimeError
….
….
at com.pega.pegarules.data.internal.clipboard.ClipboardPropertyBase.getAllReferences(ClipboardPropertyBase.java:1351)
at com.pega.pegarules.data.internal.clipboard.ClipboardPropertyBase.getAllReferences(ClipboardPropertyBase.java:1351)
at com.pega.pegarules.data.internal.clipboard.ClipboardPropertyBase.getAllReferences(ClipboardPropertyBase.java:1351)
at com.pega.pegarules.data.internal.clipboard.ClipboardPropertyBase.getAllReferences(ClipboardPropertyBase.java:1253)
at com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.clear(ClipboardPageImpl.java:661)
at com.pega.pegarules.data.internal.clipboard.ClipboardPageBase.replace(ClipboardPageBase.java:551)
at com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.replace(ClipboardPageImpl.java:484)
at com.pega.pegarules.data.internal.clipboard.ClipboardPageBase.replace(ClipboardPageBase.java:1518)
at com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.replace(ClipboardPageImpl.java:484)
at com.pega.pegarules.session.internal.mgmt.Executable.setStepPage(Executable.java:1975)
at com.pega.pegarules.pub.runtime.AbstractActivity.objOpen(AbstractActivity.java:86)
at com.pegarules.generated.activity.ra_action_pygetinteractioninternal_db247d06eefc69731c6287eedcb33f8c.step5_circum0(ra_action_pygetinteractioninternal_db247d06eefc69731c6287eedcb33f8c.java:587)
at com.pegarules.generated.activity.ra_action_pygetinteractioninternal_db247d06eefc69731c6287eedcb33f8c.perform(ra_action_pygetinteractioninternal_db247d06eefc69731c6287eedcb33f8c.java:161)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3505)
at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10563)
at com.pegarules.generated.activity.ra_action_pygetinteractioninternal_db247d06eefc69731c6287eedcb33f8c.step11_circum0(ra_action_pygetinteractioninternal_db247d06eefc69731c6287eedcb33f8c.java:956)
at com.pegarules.generated.activity.ra_action_pygetinteractioninternal_db247d06eefc69731c6287eedcb33f8c.perform(ra_action_pygetinteractioninternal_db247d06eefc69731c6287eedcb33f8c.java:289)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3505)
Steps to Reproduce
Unknown
Root Cause
pyGetInteractioninternal is in an infinite loop.
Resolution
Perform the following local-change:
Update Step 11 or the precondition in the pyGetInteractionInternal activity:
Include the additional precondition, .pyOldCallId != .pyInteractionID.
Published December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.