The RMIConnectorServer allows clients to contact and interact with the MBeans in the JMX Agent’s MBean server, as specified by JSR 160 JMX Remote.

Under JRE 1.5, RMIConnectorServer is provided by JRE 1.5. For details, see http://download.oracle.com/javase/1.5.0/docs/guide/jmx/tutorial/connectors.html.

You can specify the following RMIConnectorServer properties in the Agent properties file or as a list of prop=value pairs on the agent command line.

For example:
$GEMFIRE/bin/agent start rmi-enabled=true

The following table lists all RMIConnectorServer agent properties:

Argument Comments Default Value


IP address that the JMX Agent uses to communicate with the admin distributed system.

This is required on:
  • Multi-homed hosts (machines with multiple network cards)
  • Windows systems when using IPv6

The rmi-bind-address argument must be specified on the agent start command line if jconsole or jmanage are running on a different host.

If set to null - "" - all network addresses are used.



To enable the RMIConnectorServer, this must be true.



RMI registry port, a value in the range 0..65535.



If true, create an MX4J Naming MBean to serve as the RMI registry, and register the RMIConnector under the JNDI path /jmxconnector. More information is also available in the com.gemstone.gemfire.admin.jmx.Agent Javadocs.



Port to use for the RMIConnectorServer. If set to 0 (zero) the server socket uses a dynamically allocated port. You might want to specify the port to use when the JMX agent is behind the firewall, for example. Valid values are in the range 0..65535.

For a complete list of all agent properties, see JMX Agent Configuration Properties.