Using the Java VISUALVM remote Monitoring service __java

JDK provides us with tools to monitor server performance, such as Jconsole, Java VISUALVM, where you can use Java VISUALVM to remotely monitor the performance of WebLogic servers (memory, threads, garbage collection, etc.)

These metrics allow you to observe the running state of the server, analyze the cause of the error, such as memory overflow.

To monitor server memory changes using VMS, you first need to configure the server startup parameters, enter the WebLogic installation directory, locate the bin file in domain, and open the xx file:

After the set java_options=%java_options%, add the following configuration content:-xx:+heapdumponoutofmemoryerror-dcom.sun.management.jmxremote.port= 6001-dcom.sun.management.jmxremote.authenticate=false-dcom.sun.management.jmxremote.ssl=false

Where: +heapdumponoutofmemoryerror means that a dump file is automatically generated when the server has a memory overflow. This file records the cause of the server crash and you can analyze the problem through the file.

Again:-dcom.sun.management.jmxremote.port=6001 refers to the remote monitoring port, make sure that the port is an available port.

Other:-DCOM.SUN.MANAGEMENT.JMXREMOTE.AUTHENTICATE=FALSE-DCOM.SUN.MANAGEMENT.JMXREMOTE.SSL=FALSEG Disables SSL

-dcom.sun.management.jmxremote.ssl=false Disable Password Authentication

After the configuration is complete, restart the service.

Open VM,VM in the JDK installation directory under the bin file, the full name is: Jvisualvm.exe can also use jconsole (preferably with jdk6 more powerful)

The main interface is as follows:

Right-remote, add remote host: Enter host IP, OK.

After this address, click the right button, add JMX connection, enter IP and port Click OK Note This port is not domain port, is configured in the configuration file port

In this way, we can remotely monitor the server memory. Of course, you can also monitor the memory changes on this computer. As shown in figure: