Enabling JMX Access to a JVM: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 24: | Line 24: | ||
</font> | </font> | ||
Until Java 6, in order to make a JVM accessible to a JMX client, it had to be started with <tt>-Dcom.sun.management.jmxremote</tt> command line option. | Until Java 6, in order to make a JVM accessible to a JMX client, it had to be started with <tt>-Dcom.sun.management.jmxremote</tt> command line option. | ||
<font color=red>A JMX client can access a JVM using a "local mode" (The attach API? Is this what VisualVM uses when attaching to "Local"? or a "remote mode" (see [[Enabling JMX Access to a JVM]] below).</font> | <font color=red>A JMX client can access a JVM using a "local mode" (The attach API? Is this what VisualVM uses when attaching to "Local"? or a "remote mode" (see [[Enabling JMX Access to a JVM]] below).</font> | ||
=Attach API= | =Attach API= | ||
Revision as of 05:11, 15 October 2016
Internal
TODO
Overview
Is this the "remote mode"?
-Dcom.sun.management.jmxremote
More on this and the Attach API (Java 6 and beyond).
Parse and translate http://docs.oracle.com/javase/1.5.0/docs/guide/management/agent.html
Until Java 6, in order to make a JVM accessible to a JMX client, it had to be started with -Dcom.sun.management.jmxremote command line option. A JMX client can access a JVM using a "local mode" (The attach API? Is this what VisualVM uses when attaching to "Local"? or a "remote mode" (see Enabling JMX Access to a JVM below).
Attach API
WildFly and JMX
This is NOT the preferred method to connect to a WildFly instance with a JMX client. For more details see WildFly and JMX.