JMX Access to Domain Mode EAP 6 Server Node

External

• Accessing JMX with jconsole over SSL on EAP 6 https://access.redhat.com/solutions/632773

Internal

• WildFly and JMX
• WildFly Remoting Concepts

Overview

JBoss Remoting provides the transport of the JSR-160 Java Management Extensions (JMX) Remote API compliant implementation of a JMXConnector that can be used by standard monitoring applications to access the JMX bus.

review

In order to expose the JMX bus of a server node in domain mode, the JMX subsystem instance on the nodes sharing the same profile must be configured to expose the JMX interface on the connector defined by the Remoting subsystem.

The configuration change that enables this behavior must be applied in domain.xml, as follows:

<subsystem xmlns="urn:jboss:domain:jmx:1.3">
    ...
    <remoting-connector use-management-endpoint="false"/>
</subsystem>

The Remoting subsystem binds by default to port 4447 and authenticates against the ApplicationRealm security realm. For more details on remoting security see Remoting Concepts - Security. For details on how to add users to the ApplicationRealm, see Adding a User to the Application Realm.

Use the following URL:

service:jmx:remoting-jmx://{host_name}:{port}

In standalone mode, the port is 9999.

In domain mode, to connect the host controller use 9999 and to connect the server node, use 4447 plus any offsets.