WildFly and JMX: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
# Using the Remoting connector. For more details, see [[Remoting_WildFly_Subsystem_Concepts#Remoting_and_JMX_Access|Remoting and JMX Access]]. | # 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> | # <font color=red>Activating the JVM's built-in JMX remote access.</font>. See [[JMX#Enabling_JMX_Access_to_a_JVM|Enabling JMX Access to a JVM]]. | ||
# <font color=red>The attach API. This is visual VM uses. TODO</font> | # <font color=red>The attach API. This is visual VM uses. TODO</font> | ||
Revision as of 03:03, 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:
- 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. This is visual VM uses. TODO