Support Article
Locked synchronizers
SA-39480
Summary
A systems administrator observes thread dumps in their Pega Logfile. The SA requests assistance to identify the cause of these thread dumps.
Error Messages
No error messages are reported on screen; an examination of provided Pega log data shows one thread dump:
"WebContainer : 32" Id=7136 in RUNNABLE
BlockedCount : 67, BlockedTime : -1, WaitedCount : 74632, WaitedTime : -1
at com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl.autoChain(ClipboardPropertyImpl.java:930)
at com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl.autoChain(ClipboardPropertyImpl.java:922)
at com.pega.pegarules.data.internal.clipboard.ClipboardPropertyBase.autoChain(ClipboardPropertyBase.java:3229)
at com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl.getValue(ClipboardPropertyImpl.java:4359)
at com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl.getValue(ClipboardPropertyImpl.java:4350)
at com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl.getStringValue(ClipboardPropertyImpl.java:3539)
at com.pega.pegarules.data.internal.clipboard.XMLStream.writeXMLProperty(XMLStream.java:982)
at com.pega.pegarules.data.internal.clipboard.XMLStream.writeXMLPage(XMLStream.java:737)
at com.pega.pegarules.data.internal.clipboard.XMLStream.writeXMLProperty(XMLStream.java:956)
at com.pega.pegarules.data.internal.clipboard.XMLStream.writeXMLPage(XMLStream.java:772)
at com.pega.pegarules.data.internal.clipboard.XMLStream.writeXMLProperty(XMLStream.java:956)
at com.pega.pegarules.data.internal.clipboard.XMLStream.writeXMLPage(XMLStream.java:772)
at com.pega.pegarules.data.internal.clipboard.XMLStream.writeXMLProperty(XMLStream.java:956)
at com.pega.pegarules.data.internal.clipboard.XMLStream.writeXMLPage(XMLStream.java:772)
at com.pega.pegarules.data.internal.clipboard.XMLStream.clipboardToXML(XMLStream.java:518)
at com.pega.pegarules.data.internal.clipboard.XMLStream.clipboardToXML(XMLStream.java:493)
at com.pega.pegarules.data.internal.clipboard.WorkbenchXMLStream.<init>(WorkbenchXMLStream.java:216)
at com.pega.pegarules.data.internal.clipboard.ClipboardPageBase.getXML(ClipboardPageBase.java:2167)
at com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.getXML(ClipboardPageImpl.java:482)
at com.pega.pegarules.data.internal.clipboard.ClipboardPageBase.getXML(ClipboardPageBase.java:2152)
at com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.getXML(ClipboardPageImpl.java:482)
at com.pega.pegarules.monitor.internal.tracer.events.TraceEventBaseImpl.getPageXML(TraceEventBaseImpl.java:1077)
at com.pega.pegarules.monitor.internal.tracer.events.TraceEventBaseImpl.setPrimaryPage(TraceEventBaseImpl.java:1020)
at com.pega.pegarules.monitor.internal.tracer.events.TraceEventBaseImpl.setPrimaryPageData(TraceEventBaseImpl.java:841)
at com.pega.pegarules.monitor.internal.tracer.TraceEvent.<init>(TraceEvent.java:287)
at com.pega.pegarules.monitor.internal.tracer.TracerSessionImpl.logTraceEvent(TracerSessionImpl.java:569)
at com.pega.pegarules.session.internal.mgmt.Executable.logTraceEvent(Executable.java:1502)
at com.pega.pegarules.session.internal.mgmt.Executable.logTraceEvent(Executable.java:1488)
...
Steps to Reproduce
To reproduce this specific thread dump, the user would need to run TRACER in a busy PRPC environment - like a PROD environment.
Root Cause
A user ran the TRACER in a busy PRPC environment.
Resolution
Explained operation of the TRACER to the SA. Recommended that TRACER not be run in the PROD environment.
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.