Case Analysis of jconsole Monitoring JVM

Jconsole monitors JVM case analysis. In view of this problem, this article introduces the corresponding analysis and solution in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible method.

Jconsole Monitoring JVM

Need to open vim catalina.sh under tomcat/bin

In # OS specific support. $var _ must_ be set to either true or false. Add on it.

JAVA_OPTS= "- Xms128m-Xmx128m-Xss1024K-XX:PermSize=128m-XX:MaxPermSize=128m-Djava.rmi.server.hostname=192.168.198.136-Dcom.sun.management.jmxremote-Dcom.sun.management.jmxremote.port=1091-Dcom.sun.management.jmxremote.ssl=false-Dcom.sun.management.jmxremote.authenticate=false"

Where-Xms128m-Xmx128m-Xss1024K-XX:PermSize=128m-XX:MaxPermSize=128m is the JVM heap memory configuration

-Djava.rmi.server.hostname=192.168.198.136-Dcom.sun.management.jmxremote-Dcom.sun.management.jmxremote.port=1091 is the relevant setting for RMI

-Dcom.sun.management.jmxremote.ssl=false-Dcom.sun.management.jmxremote.authenticate=false is a security policy that does not require a user name and password when monitoring the server with jconsole

192.168.198.136 is the server IP that needs to be monitored

1091 is the port number, which can be changed at will

two。 Need to modify vim / etc/hosts to change 127.0.0.1 to the corresponding IP

3. Connect

This is the answer to the question about jconsole monitoring JVM instance analysis. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel for more related knowledge.