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

Unable to configure dynamic nodes in SMA



In a cloud based platform, applications are deployed through the docker.

Post 7.4 upgrade, when the prsysmgmt.war is at the same location as the application WAR, the System Management Application (SMA) configuration works correctly. However, if the SMA WAR is a separate container, unable to perform the Java Remote Method Invocation (RMI) configuration.

Error Messages

com.pega.jmx.ui.util.JMXClientException: Exception getting MBean Server connection. Cannot connect to the server with specified settings 
Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: ; nested exception is: Connection refused (Connection refused)]

Steps to Reproduce

  1. Deploy SMA WAS as a separate container.
  2. Configure the application nodes.

Root Cause

Enable the Java Management Extensions (JMX)  port.


Perform the following local-change:

Set the following,

Published August 15, 2019 - Updated December 2, 2021

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