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

pr_sys_statusnodes entries pull incorrect address



Pega pr_sys_statusnodes table displays and points to middleware Docker servers instead of WAS servers.

Error Messages

Not Applicable

Steps to Reproduce


Root Cause

Since the server has more than one NIC, it is necessary to specify the IP which must be retrieved or the range of the IP in the prconfig.xml.


Perform the following local-change:

Add the IP in prconfig.xml using any one of the following syntaxes: <env name="cluster/hazelcast/members" value="lclinbw7" /> -- single value, hostname
<env name="cluster/hazelcast/members" value="xx.yy.zz.ww," /> -- list of values, IP
<env name="cluster/hazelcast/members" value="" /> -- range of values (.85-.99)

Published December 5, 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