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

new rule versions not appearing on other nodes

SA-24179

Summary



After upgrading Pega PRPC from version 7.1.8 to 7.1.9, every time we deploy new rules in the QA, UAT and Prod environments, we need to restart Pega in order to be able to see and use the new version of such rules.
 

Error Messages



No error messages are present in the log files during the deploy.

Steps to Reproduce



- Deploy a RAP from Node 1;
- Access the application on Node 2, 3 or 4;
- the old version of the application is presented, instead of the new one just deployed.

Root Cause



The system pulse was changed to default to cluster in 7.1.9. The system pulse agent was not running on all the nodes in the environment.

Resolution



The solution is to add the following configuration setting <env name=”initialization/pulse/transport” value=”cluster” /> to ensure that that all the configuration is changed from database to cluster and reboot the whole cluster to make sure that cluster is using the default protocol.
Suggest Edit

Published June 30, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

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
Contact us