WildFly and JMX: Difference between revisions
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
# '''The preferred method''': using the Remoting connector. For more details, see [[Remoting_WildFly_Subsystem_Concepts#Remoting_and_JMX_Access|Remoting and JMX Access]]. | # '''The preferred method''': using the Remoting connector. For more details, see [[Remoting_WildFly_Subsystem_Concepts#Remoting_and_JMX_Access|Remoting and JMX Access]]. | ||
# <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. | # <font color=red>The attach API. Is this what VisualVM uses when attaching to "Local"?. TODO</font> | ||
Revision as of 03:17, 15 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