WildFly and JMX: Difference between revisions
Jump to navigation
Jump to search
| Line 22: | Line 22: | ||
| '''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]] | | '''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 [[JMX#Remote_Access_to_a_JMX_Server|Remote Access to a JMX Server]] section. | |||
Revision as of 21:05, 17 June 2017
Internal
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.