WildFly and JMX: Difference between revisions
| (6 intermediate revisions by the same user not shown) | |||
| Line 7: | Line 7: | ||
=Overview= | =Overview= | ||
Each | Each JBoss instance has a JMX bus with various JMX MBeans deployed on it. The JMX MBeans expose management functionality, which can be used for monitoring or operations. For a JBoss instance running in standalone mode, there is just one JMX bus to access - the one of the standalone instance. However, for a JBoss instance running in domain mode, the JMX buses of a domain and host controller expose access to a different functionality than the JMX buses of the server nodes, and different procedures are required to access them. | ||
For a | |||
=Procedures= | =Procedures= | ||
| Line 16: | Line 14: | ||
| || '''EAP 6''' || '''EAP 7''' || '''JDG 7''' | | || '''EAP 6''' || '''EAP 7''' || '''JDG 7''' | ||
|- | |- | ||
| '''standalone mode instance''' || [[JMX Access to Standalone EAP 6]] || [[JMX Access To Standalone EAP 7]] | | '''standalone mode instance''' || [[JMX Access to Standalone EAP 6|JMX Access Procedure]] || [[JMX Access To Standalone EAP 7|JMX Access Procedure]] | ||
|- | |- | ||
| '''domain mode host controller''' || [[JMX Access to EAP 6 Host Controller]] || [[JMX Access to EAP 7 Host Controller]] | | '''domain mode host controller''' || [[JMX Access to EAP 6 Host Controller|JMX Access Procedure]] || [[JMX Access to EAP 7 Host Controller|JMX Access Procedure]] | ||
|- | |- | ||
| '''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 Procedure]] || [[JMX Access to Domain Mode EAP 7 Server Node|JMX Access Procedure]] || [[JMX Access to Domain Mode JDG 7 Server Node|JMX Access Procedure]] | ||
|} | |} | ||
=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. [[Novaordis-jmx|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|novaordis-jmx]] uses the JMX remoting API in conjunction with WildFly remoting JMX capabilities, see: | |||
{{Internal|Accessing WildFly JMX Bus Remotely with novaordis-jmx|Accessing WildFly JMX Bus Remotely with novaordis-jmx}} | |||
Latest revision as of 21:38, 7 July 2017
Internal
Overview
Each JBoss instance has a JMX bus with various JMX MBeans deployed on it. The JMX MBeans expose management functionality, which can be used for monitoring or operations. For a JBoss instance running in standalone mode, there is just one JMX bus to access - the one of the standalone instance. However, for a JBoss instance running in domain mode, the JMX buses of a domain and host controller expose access to a different functionality than the JMX buses of the server nodes, and different procedures are required to access them.
Procedures
| EAP 6 | EAP 7 | JDG 7 | |
| standalone mode instance | JMX Access Procedure | JMX Access Procedure | |
| domain mode host controller | JMX Access Procedure | JMX Access Procedure | |
| domain mode server node | JMX Access Procedure | JMX Access Procedure | JMX Access Procedure |
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: