WildFly and JMX

Internal

• WildFly Concepts
• JSR 160 Java Management Extensions (JMX) Remote API
• Enabling JMX Access to a JVM

Overview

Each WildFly instance has a JMX bus with various JMX MBeans plugged in. The JMX MBeans expose management functionality, which can be used in monitoring or operations.

For a WildFly instance running in standalone mode, there is just one JMX bus to access - the one of the standalone instance. However, for a WildFly instance running in domain mode, the procedure to access the JMX bus of the host controller is different from the procedure of to access the JMX bus of the server node.

Procedures

	EAP 6	EAP 7
standalone mode instance	standalone eap 6	standalone eap 7
domain mode - host controller	host controller eat 6	host controller eat 7
domain mode - server node	server node eap 6	server node eap 7

jconsole

Visual VM

Data Dog

The JMX bus can be accessed in three ways:

1. The preferred method: using the Remoting connector. For more details, see Remoting and JMX Access.
2. Activating the JVM's built-in JMX remote access.. See Enabling JMX Access to a JVM.
3. The attach API. Is this what VisualVM uses when attaching to "Local"?. TODO