Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Cluster nodes are not in sync -agent running issue



User is having Pega 7.1.7 2x2 cluster node, where application is working fine in one node but not working in second node.

Mainly the inboundsmsflow agent is not working properly in all nodes.

Application functionality not work properly in one node where as in another node it is working fine in a cluster node environment.

User can see errors in the logs related to agents.

Error Messages

Some error messages are present.
PegaMKT-Engine 14 InboundSMSOfferFlow Advanced Every 30 s Exception at 20170326T201836.257 GMT: caught exception during autocommit check at at at at at at at com.pegarules.generated.activity.ra_action_associatecustomer_7993a9d9ff7d7b37c3d6f51aa007b5b1.step4_circum0( at com.pegarules.generated.activity.ra_action_associatecustomer_7993a9d9ff7d7b37c3d6f51aa007b5b1.perform( at com.pega.pegarules.session.internal.mgmt.Executable.doActivity( at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity( at com.pegarules.generated.activity.ra_action_initiateoffer_dacbe3c0f55262b970926f56eb699275.step5_4_circum0( at com.pegarules.generated.activity.ra_action_initiateoffer_dacbe3c0f55262b970926f56eb699275.step5_0_circum0_PegaMKT_Data_Inbound_SMS( at com.pegarules.generated.activity.ra_action_initiateoffer_dacbe3c0f55262b970926f56eb699275.perform( at com.pega.pegarules.session.internal.mgmt.Executable.doActivity( at com.pega.pegarules.session.internal.async.agent.QueueProcessor.runActivity( at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute( at at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock( at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked( at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked( at at at$ at Caused by: java.sql.SQLRecoverableException: Closed Connection at oracle.jdbc.driver.PhysicalConnection.getAutoCommit( at at ... 23 more

2017-03-30 10:20:39,494 [ saryppapp1] [ STANDARD] [ ] [ ZainNBA:01.01.01] (onse.PegaMKT_Work_Offer.Action) ERROR - Error in Obj-Open Cannot open or save instances of class Data-BatchOutPR89--the class might be abstract, or it might have no defined keys, or it might descend from Code-.

2017-03-30 12:21:41,692 [ pool-18-thread-1] [ STANDARD] [ ] [ ] (dnode.api.DNodeServiceListener) ERROR - Cannot initialize DNode context and start Cassandra, PRPC continuing as non-DNode
com.pega.dsm.dnode.api.DNodeException: Cannot bootstrap cassandra
at com.pega.dsm.dnode.impl.cassandra.Cassandra.bootstrap(
at com.pega.dsm.dnode.api.DNodeBootstrap.bootstrap(
at com.pega.dsm.dnode.api.DNodeServiceListener$
at java.util.concurrent.Executors$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$
Caused by: java.lang.IllegalStateException: Dnode ports are in use, looks like another instance of dnode is running on this machine
at com.pega.dsm.dnode.impl.cassandra.Cassandra.bootstrap(
... 7 more

Steps to Reproduce

Not Applicable

Root Cause

A defect or configuration issue in the operating environment.

The multinode environment has same IP and temporary directory for multiple nodes, causing PRPC to generate same nodeid for multiple prpc jvms.


Here’s the explanation for the reported behavior:

1. Setup only one dnode per system.
2. Update weblogic startup scripts to define separate Pega Temp dir location for every managed servers.
3. Update prconfig.xml to add env variable "cluster/hazelcast/interfaces" to set external IP that is accessible from other systems in the cluster.

Published May 6, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us