WildFly and JMX: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
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. | 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 | |||
<font color=red> | |||
The JMX bus can be accessed in three ways: | The JMX bus can be accessed in three ways: | ||
| Line 18: | Line 46: | ||
# <font color=red>Activating the JVM's built-in JMX remote access.</font>. See [[Enabling JMX Access to a JVM]]. | # <font color=red>Activating the JVM's built-in JMX remote access.</font>. See [[Enabling JMX Access to a JVM]]. | ||
# <font color=red>The attach API. Is this what VisualVM uses when attaching to "Local"?. TODO</font> | # <font color=red>The attach API. Is this what VisualVM uses when attaching to "Local"?. TODO</font> | ||
</font> | |||
Revision as of 16:20, 18 October 2016
Internal
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:
- The preferred method: using the Remoting connector. For more details, see Remoting and JMX Access.
- Activating the JVM's built-in JMX remote access.. See Enabling JMX Access to a JVM.
- The attach API. Is this what VisualVM uses when attaching to "Local"?. TODO