Support Article
Session Recovery (HA crash) does not work completely
SA-78760
Summary
Session Recovery during a High Availability Crash event does not work completely. The Pega Customer Service (CS) application does not restore the Operators session for Open and Work in Progress Interactions. Additionally, unexpected pages are rendered instead of the expected pages.
Error Messages
[ES PassivationDaemon] [STANDARD] [ ] [ ] (mgmt.base.NodeRequestorMgt) ERROR - Environmental error while timing out requestor; Will re-enqueue
com.pega.pegarules.session.external.mgmt.PassivationException: Unable to passivate requestor 'HRDDHS1JS8L0MYA1F2ZLH4KJ49CKB8PNJ'
at com.pega.pegarules.session.internal.mgmt.base.NodeRequestorMgt.cleanupConditionally(NodeRequestorMgt.java:1399) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.base.NodeRequestorMgt.cleanupInner(NodeRequestorMgt.java:1318) ~[prprivate.jar:?]
at sun.reflect.GeneratedMethodAccessor125.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_151]
at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_151]
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1338) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1075) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:930) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.base.NodeRequestorMgt.cleanupRequestor(NodeRequestorMgt.java:1294) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.base.NodeRequestorMgt.cleanupRequestor(NodeRequestorMgt.java:1288) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.base.NodeRequestorMgt.timeoutRequestorThrowingErrors(NodeRequestorMgt.java:1271) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.base.NodeRequestorMgt.processPassivationQueue(NodeRequestorMgt.java:2717) ~[prprivate.jar:?]
Steps to Reproduce
Scenario A:
Access the Member Interaction screen. An Unknown screen displays after the crash.
Scenario B:
Configure two Service items that are open while viewing a member. Observe the 'Authorization Request' screen, and the Loss Context on the Provider and Member data. Additionally, there are no Service items in the 'Add Task' list.
Note: Both the scenarios are preceded by an unexpected login page.
Root Cause
A defect in Pegasystems’ code or rules.
Resolution
Apply HFix-45537.
Published May 1, 2019 - 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.