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

Changes made to a rule in a node do not reflect in another node

SA-92141

Summary



Two nodes (For example, Node 1 and Node 2) are run on an application. User modifies a rule in Node 1. However, the changes do not reflect in Node 2. System Pulse runs in both the nodes. The issue does not occur after the server restart. However, the issue reoccurs when user makes changes in rule.


Error Messages



Not Applicable


Steps to Reproduce



Unknown


Root Cause



The two nodes ran on the same IP address and port. This prevented cluster formation. However, hazelcast is able to connect to each node using TCP/IP which requires a unique IP address or a port.


Resolution



Perform the following local-change:
Change the port or IP address of one of the nodes.




 

Published December 2, 2021

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.

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