JMX: Difference between revisions
Jump to navigation
Jump to search
Line 7: | Line 7: | ||
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. For Java 6 and beyond, a JMX client can connect using the Attach API. | 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. For Java 6 and beyond, a JMX client can connect using the Attach API. | ||
<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> | |||
A JMX client can access a JVM using a "local mode" ( | |||
=Enabling JMX Access to a JVM= | =Enabling JMX Access to a JVM= |
Revision as of 03:23, 15 October 2016
External
Internal
Overview
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. For Java 6 and beyond, a JMX client can connect using the Attach API.
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).