|Using Java Management Extensions (JMX) / Federated MBean Architecture|
GemFire XD programmatically emulates out-of-box Java 1.6 JMX and creates a JMXServiceURL with RMI Registry and RMI Connector ports on all the JMX manager node. Managed nodes do not start an RMI connector by default, and do not require a connector for management via the manager node.
You can configure a specific connection port and address when launching a process that will host the GemFire XD JMX Manager by specifying values for the jmx-manager-bind-address and jmx-manager-port, which defines the RMI connection port.
The default GemFire XD JMX Manager RMI port is 1099. You may need to modify this default if 1099 is reserved for other uses.
If for some reason you need to use standard JMX RMI in your deployment for other monitoring purposes, set the GemFire XD property jmx-manager-port to 0 on any members where you want to use standard JMX RMI.
If you use out-of-the-box JMX RMI instead of starting an embedded GemFire XD JMX Manager, you should consider setting -Dsun.rmi.dgc.server.gcInterval=Long.MAX_VALUE-1 when starting the JVM for customer applications and client processes. Every GemFire XD process internally sets this setting before creating and starting the JMX RMI connector in order to prevent full garbage collection from pausing processes.