Support Article
Repeated passivation exception in logs
SA-12229
Summary
Administrators are seeing a passivation daemon exception in the logs very frequently. This is cluttering the logs and making them difficult to read.
Error Messages
2015-07-06 13:11:41,508 [.PRPCWorkManager : 7] [ STANDARD] [ ] [ PegaRULES:07.10] ( mgmt.base.NodeRequestorMgt) ERROR - Passivation Daemon; Requestor: HCA02D8C2D244D9B40ACF6B5DCB72CE8F encountered error during passivation; will re-enqueue
com.pega.pegarules.pub.PRRuntimeException: Method Invocation exception
. . .
Caused by:
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor64.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1203)
... 34 more
Caused by:
java.lang.NoClassDefFoundError: com/pega/pegarules/session/internal/mgmt/QuiesceManager$QuiesceActivityCallForRequestor
at com.pega.pegarules.session.internal.mgmt.QuiesceManager$QuiesceActivityCall.withRequestor(QuiesceManager.java:376)
at com.pega.pegarules.session.internal.mgmt.base.NodeRequestorMgt.cleanupInner(NodeRequestorMgt.java:1065)
... 38 more
Steps to Reproduce
Not Appplicable
Root Cause
The root cause of this problem is a defect in Pegasystems’ code/rules. An issue in the passivation daemon produces the error message.
Resolution
This issue is resolved in release 7.1.6 and later versions.
More information is available in the resolved issues section of the release notes for 7.1.6.
Published July 17, 2015 - 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.