Support Article
MDB Listeners stop processing and cannot be restarted
SA-55565
Summary
Pega 7.3 is run on WebSphere Application Server (WAS) 8.5.5.12 which is connected to an IBM WebSphere MQ Queue Manager.
MDB Listeners listen for incoming messages on several different IBM WebSphere MQ Queues.
When running MDB Listeners for several weeks, the listeners stop processing. Unable to restart the listeners without restarting the WAS.
Error Messages
Java "Stack-Trace" of the running Application Server is obtained.
Based upon the contents of this file, the reason that the MDB Listeners have stopped processing seems to be because of a Java "Deadlock" between code within:
...
at com/pega/pegarules/priv/util/KeybasedLock$RequestToken.lock(KeybasedLock.java:170(Compiled Code))
at com/pega/pegarules/priv/util/KeybasedLock.lock(KeybasedLock.java:93(Compiled Code))
at com/pega/pegarules/exec/internal/basic/dictionary/ConclusionTypeCacheImpl$ConclusionKeyBasedLock.lock(ConclusionTypeCacheImpl.java:1287(Compiled Code))
...
and
...
at com/pega/pegarules/exec/internal/declare/infengine/cbi/DeclarativeCacheManagerImpl.getPropertyUsageType(DeclarativeCacheManagerImpl.java:922(Compiled Code))
at com/pega/pegarules/exec/internal/declare/infengine/cbi/DeclarativeCacheManagerImpl.isPropertyDeclarativeSource(DeclarativeCacheManagerImpl.java:715(Compiled Code))
at com/pega/pegarules/data/internal/dictionary/PropertyInfoConclusionImpl.initialize(PropertyInfoConclusionImpl.java:298)
...
Steps to Reproduce
Unknown
Root Cause
A defect in Pegasystems’ code or rules.
Deadlock between Declarative Cache and Conclusion Cache while deploying a new application.
Resolution
Perform the following local-change:
Disable high usage agents while deploying new applications.
Published August 1, 2018 - 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.