Support Article
Unable to configure dynamic nodes in SMA
SA-81324
Summary
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: java.net.ConnectException: Connection refused (Connection refused)]
Steps to Reproduce
- Deploy SMA WAS as a separate container.
- Configure the application nodes.
Root Cause
Enable the Java Management Extensions (JMX) port.
Resolution
Perform the following local-change:
Set the following,
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=9010
-Dcom.sun.management.jmxremote.local.only=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
Published August 15, 2019 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.