WildFly and JMX: Difference between revisions
Jump to navigation
Jump to search
| Line 23: | Line 23: | ||
|} | |} | ||
[[Remoting_WildFly_Subsystem_Concepts#Remoting_and_JMX_Access]] | |||
[[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> | </font> | ||
Revision as of 16:23, 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 |
Remoting_WildFly_Subsystem_Concepts#Remoting_and_JMX_Access
- The attach API. Is this what VisualVM uses when attaching to "Local"?. TODO