Support Article
Server crashed and produced thread dumps
SA-41417
Summary
Development instance crashed during active development duration. The issue stems from what seems like a resource intensive reference property use.
Error Messages
The thread dumps are caused by a large stack of these getAllReferences and putAll method calls:
at com.pega.pegarules.data.internal.clipboard.ClipboardPropertyBase.getAllReferences(ClipboardPropertyBase.java:1463)
at com.pega.pegarules.data.internal.clipboard.ClipboardPropertyBase.getAllReferences(ClipboardPropertyBase.java:1510)
…
at com.pega.pegarules.data.internal.clipboard.ClipboardPageBase.putAll(ClipboardPageBase.java:1202)
at com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.putAll(ClipboardPageImpl.java:484)
This engine stack is called by your_Activity executed as part of your_flow.
Steps to Reproduce
Not Applicable
Root Cause
An issue in the custom application code or rules.
Resolution
Perform the following local-change: Inspect and remediate the reference property calls from your_Activity executed as part of your_flow.
Published August 26, 2017 - 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.