Support Article
Deadlock detected during a class load - JVM fails
SA-46700
Summary
The WebLogic console displays JVM failure and the log reveals a deadlock. Few threads display as blocked, during PRClassLoaderDB calls, in the thread dump.
Error Messages
<Critical> <WebLogicServer> <BEA-000394> <Deadlock detected:
[deadlocked thread] [ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)':
---------------------------------------------------------------------------------------------------
Thread '[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'' is waiting to acquire lock 'com.pega.pegarules.exec.internal.util.classloader.PRClassLoaderDB@2dfbb755' that is held by thread '[ACTIVE] ExecuteThread: '16' for queue: 'weblogic.kernel.Default (self-tuning)''
Stack trace:
------------
com.pega.pegarules.exec.internal.util.classloader.PRClassLoaderDB.injectKnownClass(PRClassLoaderDB.java:1312)
com.pega.pegarules.exec.internal.util.PRClassLoaderUtilsImpl.injectKnownClass(PRClassLoaderUtilsImpl.java:356)
com.pega.pegarules.generation.internal.compiler.ClassloaderInjectingCompilationSaver.injectClasses(ClassloaderInjectingCompilationSaver.java:58)
com.pega.pegarules.generation.internal.compiler.QueuedCompilationSaver.saveClasses(QueuedCompilationSaver.java:70)
com.pega.pegarules.generation.internal.compiler.PRCompilerUtil.notifyCompilationListeners(PRCompilerUtil.java:779)
com.pega.pegarules.generation.internal.compiler.PRCompilerEclipse._compile_privact(PRCompilerEclipse.java:613)
com.pega.pegarules.generation.internal.compiler.PRCompilerEclipse.compile(PRCompilerEclipse.java:514)
Steps to Reproduce
Unknown
Root Cause
A defect in Pegasystems’ code or rules.
Resolution
Apply HFix-38661.
Published December 5, 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.