JVM monitoring tools-Introduction to several common tools
Introduction to JVM monitoring tools
Jdk provides a powerful GUI-based jvm monitoring tool, which can be seen in the jdk bin directory, such as jconsole, jvisualvm, and oracle jrockit jvm's jrmc.exe.
Introduction:
GUI tools |
Supported types |
Local GUI running version (JRE) |
Tested JVM version |
Jconsole |
Jvm, jrockit jvm |
1.5 or above |
1.5 or above |
Jvisualvm |
Jvm |
1.5 or above |
1.5 or above |
Jrmc |
Jrockit jvm |
1.4.2 and later |
1.4.2 and later |
1. jvm: sun's jvm (Common jvm) |
2. jrockit jvm: oracle (weblogic default) |
Remark 1: jrmc: Abbreviation of Oracle JRockit Mission Control
NOTE 2: Make sure that the tool jvm is consistent with the tested jvm version.
NOTE 3: JDK1.7 and later versions only support Oracle jdk. Oracle has transformed jrmc into a jmc tool and can only be used by jconsole and jmc tools.
1. Monitor local jvm and remote jvm
Monitor the local jvm and start any GUI tool. The tool automatically queries the local jvm process. However, note that only the jvm started by the current user (non-Administrator) can be monitored here, no permission to detect jvm started by other users.
2. Monitor remote jvm. A remote service must be started on the tested jvm (each tool has multiple services)
3. Modify the middleware configuration and add the JAVA_OPTIONS parameter to the jvm:
Weblogic jrockit jvm enables monitoring service parameters:
-Xmanagement: ssl = false, authenticate = false, port = 7091 --- jdk1.5 + (weblogic10)
-Xmanagement: port = 7091-jdk1.4.2 (weblogic8.1)
Sun jvm enables monitoring service parameters:
-Dcom. sun. management. JMX remote. port = 8899
-Dcom. sun. management. jmxremote. ssl = false
-Dcom. sun. management. jmxremote. authenticate = false
Ports are temporarily occupied and can be customized.