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 into it. The JMX MBeans expose management functionality, which can be used for 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	JDG 7
standalone mode instance	JMX Access to Standalone EAP 6	JMX Access To Standalone EAP 7
domain mode host controller	JMX Access to EAP 6 Host Controller	JMX Access to EAP 7 Host Controller
domain mode server node	JMX Access to Domain Mode EAP 6 Server Node	JMX Access to Domain Mode EAP 7 Server Node	JMX Access to Domain Mode JDG 7 Server Node

Programmatic JMX Access

The WildFly JMX bus can be accessed programmatically using standard JMX remoting API, as described in the Remote Access to a JMX Server section. novaordis-jmx is a library that provides a thin layer of functionality in top of the client-side JMX remoting API, with the intention to facilitate programmatic JMX access to a remote JMX bus. For a detailed discussion on how novaordis-jmx uses the JMX remoting API in conjunction with WildFly remoting JMX capabilities, see:

Accessing WildFly JMX Bus Remotely with novaordis-jmx