Support Article

PRNodeImpl init failed at environment startup

SA-42157

Summary



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>
com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed
....
Caused by: java.lang.NullPointerException
at com.pega.pegarules.cluster.internal.PRClusterHazelcastImpl.initialize(PRClusterHazelcastImpl.java:555)
at com.pega.pegarules.cluster.internal.PRClusterImpl.getInstance(PRClusterImpl.java:247)
at com.pega.pegarules.cluster.internal.PRClusterProviderImpl.getInstance(PRClusterProviderImpl.java:96)
at com.pega.pegarules.session.internal.mgmt.PRNodeImpl.joinCluster(PRNodeImpl.java:2595)
at com.pega.pegarules.session.internal.mgmt.PRNodeImpl.initializeSystem(PRNodeImpl.java:908)
at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:378)
... 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.

Resolution



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


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.