JMX connection error: MBean Server

In complex deployment configurations the management console may not automatically connect to the JMX server for a component such as a pool manager or a web tier. An indicator of connection failure is an error message in this format: Copy Problem connecting to MBean Server using RMI protocol at [host]:[port] To ensure connection, in the configuration file of the component that the management console is not able to reach, administrators can add the parameter java.rmi.server.hostname. The parameter should be set to the host name identified in the error message. Example The management console installed on machine server1.example.com is not able to connect to pool manager x installed on poolx.example.com. Try adding the following setting to the JMX_OPTS line of the pool manager configuration file mgrenv (mgrenv.bat) installed on poolx.example.com: Copy -Djava.rmi.server.hostname=poolx.example.com For reference, before the hostname parameter is added, the JMX_OPTS line might look like this in the file: Copy set JMX_OPTS=-Dcom.sun.management.jmxremote.port=8088 -Dcom.sun.management.jmxremote.login.config=MgmtLdapConfig -Djava.security.auth.login.config=ldap.config -Dcom.sun.management.jmxremote.ssl=false