Support Article
Frequent nodes getting terminated due to Hazelcast error
SA-68067
Summary
Pega nodes are terminated frequently with PresenceRuntimeException.
Error Messages
[ES PassivationDaemon] [STANDARD] [ ] [ ] (ence.PresenceDataGridHazelcast) ERROR - replace(): Presence Record update operation failed. Exceeded maximum attempts.Arguments:Operator:pega_webservice,Tenant:shared,CustomCategory:null [ES PassivationDaemon] [STANDARD] [ ] [ ] (platform.message.CoreMessage) WARN - The message exceeds recommended size of :8000. [onStateTrackerDaemon] [ ] [ ] [ ] (ence.PresenceDataGridHazelcast) ERROR - replace(): Presence Record update operation failed. Exceeded maximum attempts.Arguments:Operator:pega_webservice,Tenant:shared,CustomCategory:null [onStateTrackerDaemon] [ ] [ ] [ ] (.PresenceLifeCycleEventManager) ERROR - Failed to update session state for requestor with ID: HABCDXYZ com.pega.pegarules.priv.presence.PresenceRuntimeException: replace(): Presence Record update operation failed. Exceeded maximum attempts.Arguments:Operator:pega_webservice,Tenant:shared,CustomCategory:null at com.pega.pegarules.cluster.internal.presence.PresenceDataGridHazelcast.handleIfMaxAttemptsExceeded(PresenceDataGridHazelcast.java:212) ~[prcluster.jar:?] at com.pega.pegarules.cluster.internal.presence.PresenceDataGridHazelcast.replace(PresenceDataGridHazelcast.java:196) ~[prcluster.jar:?] at com.pega.pegarules.session.internal.presence.PresenceDataProcessorImpl.updateSessionStateToDisconnected(PresenceDataProcessorImpl.java:268) ~[prprivate.jar:?] at com.pega.pegarules.session.internal.presence.PresenceLifeCycleEventManager.updateSessiontoDisconnectedIfIdle(PresenceLifeCycleEventManager.java:140) ~[prprivate.jar:?] at com.pega.pegarules.session.internal.presence.PresenceSessionStateTrackerDaemon.identifyDisconnectedSessions(PresenceSessionStateTrackerDaemon.java:150) ~[prprivate.jar:?] at com.pega.pegarules.session.internal.presence.PresenceSessionStateTrackerDaemon.run(PresenceSessionStateTrackerDaemon.java:129) ~[prprivate.jar:?]
Steps to Reproduce
Not Applicable
Root Cause
A defect in Pegasystems’ code or rules.
The same operator_id was used to create multiple sessions. The sessions timed out while the session state daemon attempted to update them.
Resolution
Perform the following local-change:
Create the below Dynamic System Setting (DSS) and restart all the nodes.
Purpose: prconfig/operatorpresence/enabled/default
Owning Ruleset: Pega-Engine
Value: false
Published November 29, 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.