JRockit Mission Control (JRMC) Console Connectivity (R28) through Firewall

When connecting JRMC to a remote machine protected by a firewall, the following options can help:

• Enable JRockit management (details on JRockit -X Command Line Options): -Xmanagement:autodiscovery=true,ssl=false,authenticate=false,port=7491,interface=<IP address or DNS hostname>
• port - the port on which JRockit opens the management port
• interface - the port will listen on all addresses, but JRockit will accept only requests for the IP address/hostname defined here
• Specify a listen host for the java RMI server - this host is reported by the JVM back to the console and used for further connectivity. If not defined on multi-IP machines this can cause connectivity issues, as the first IP is always returned, even if a virtual IP was used to connect to the server. JVM option: -Djava.rmi.server.hostname=<IP address or DNS hostname>
• Choose a port for MemLeak and configure it on the client (In JRMC client, go to Window/Preferences/JRockit Mission Control/Memory Leak Detector/Communication and choose "Use fixed port" and set the value to the port chosen) - I would recommend a single port for all servers, so you do not have to reconfigure your client each time you connect (usually you don't need to start MemLeak on more than one node of a cluster).