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

PRNodeImpl init failed at environment startup



In a multi-node environment, not all nodes start after stopping and restarting the system.

Error Messages

2017-08-02 11:32:43,887 <server name>] [ STANDARD] [ ] [ ] ( etier.impl.EngineStartup) ERROR - PegaRULES initialization failed. Server: <server name> PRNodeImpl init failed
Caused by: java.lang.NullPointerException
at com.pega.pegarules.cluster.internal.PRClusterHazelcastImpl.initialize(
at com.pega.pegarules.cluster.internal.PRClusterImpl.getInstance(
at com.pega.pegarules.cluster.internal.PRClusterProviderImpl.getInstance(
at com.pega.pegarules.session.internal.mgmt.PRNodeImpl.joinCluster(
at com.pega.pegarules.session.internal.mgmt.PRNodeImpl.initializeSystem(
at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(
... 93 more

Steps to Reproduce

Not applicable

Root Cause

Two of the eight nodes in the environment reside on machines which have more than one NIC and each NIC has a different ip address.
On these two nodes Hazelcast is choosing an ip different from the rest of the members of the Hazelcast cluster.


The DSS Pega-Engine • prconfig/cluster/hazelcast/interface/default was defined with value <ip address>.*
so that all nodes in the environment will use the same ip address when joining the Hazelcast cluster.

Published August 26, 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