WildFly and JMX: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 8: | Line 8: | ||
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. | 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. | |||
The JMX bus can be accessed in three ways: | The JMX bus can be accessed in three ways: | ||
Revision as of 16:14, 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.
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