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

SMA stops working as node IDs change after restarting JVM

SA-73448

Summary


 

System Management Application (SMA) stops working as the node IDs change after restarting the JVM.


Error Messages


 

com.pega.jmx.ui.util.JMXClientException: No MBeans found for the node your_pega_node


Steps to Reproduce


 

Restart the JVM.


Root Cause



The node ID is dependent on the Pega system name, temporary directory location and hostname, by default. If any of these change, the node ID will change.

Resolution



Perform the following local-change:
Set the node ID statically by using the below JVM argument:

-Didentification.nodeid=<node_id>

 

Suggest Edit

Published February 20, 2019 - Updated December 2, 2021

Did you find this content helpful? Yes No

100% found this useful

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