WildFly and JMX: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 3: | Line 3: | ||
* [[WildFly Concepts]] | * [[WildFly Concepts]] | ||
* [[JSR 160 Java Management Extensions (JMX) Remote API]] | * [[JSR 160 Java Management Extensions (JMX) Remote API]] | ||
* [[Enabling JMX Access to a JVM]] | |||
=Overview= | =Overview= | ||
Revision as of 16:09, 18 October 2016
Internal
Overview
Each WildFly instance includes a JMX bus with various JMX MBeans attached. The JMX MBeans expose management functionality, which can be used in monitoring or operations.
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