Support Article
Node ID was reset automatically
SA-20242
Summary
User sees new Node ID created in logs with PRPC 6.2 SP2.
Error Messages
No error messages. INFO debug log entry below
19 Jan 2016 21:20:04,987 [ rf51p0c] [ STANDARD] [ ] ( internal.mgmt.PRNodeImpl) INFO - Created new node: "rf51p0c pega created 2016-01-20 02:19:01.893 GMT", [ba9db9571eda029e0f21d8304f308e47]
19 Jan 2016 21:20:06,275 [ rf51p0c] [ STANDARD] [ ] ( internal.mgmt.PRNodeImpl) INFO - Node Identification: "rf51p0c pega created 2016-01-20 02:19:01.893 GMT"; Node Id: ba9db9571eda029e0f21d8304f308e47
Steps to Reproduce
Not Applicable.
Root Cause
The pxSystemNodeID value is a hashed value of the PRPC systemname, the server's host name and the PegaTemp directory path.
During server or JVM startup if the PRPC engine detects any change in value of either the PRPC system name, server's host name or the PegaTemp directory path it will generate a new hash for the pxSystemNodeID.
This is the designed behavior. However, if user has Listeners (JMS, JMSMDB, File and so on) in the application which is using a "Node based startup" startup mechanism then the listeners must be manually changed to update the new node ID.
Resolution
If user has listeners, JMS, JMSMDB, File and so on, in your application which are using a "Node based startup" startup mechanism then the listeners must be manually changed to update the new node ID.
Published March 4, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.