1, Jetty server adds jmx, jmx-remote module
modify the configuration file start.ini corresponding to the jetty server and add the following two lines
�Cmodule=jmx�Cmodule=jmx-remote
2. Edit $JETTY_HOME/etc/jetty-jmx-remote.xml to modify the jmxrmihost monitoring address and jmxrmiport Monitoring port
If you don’t modify it, the default listening address is localhost, which is 127.0.0.1, The port is 1099
If there are multiple instances of jetty on a server, port Can not conflict.
After the above configuration is completed, the jmx monitoring of zabbix cannot be used to monitor by default, which is not the same as tomcat. I use
cmdline-jmxclient-0.10.3.jar for monitoring, you need to write your own monitoring script and custom monitoring template
#java-jar cmdline-jmxclient-0.10.3.jar- 127.0.0.1:1099 java.lang:type=Threading# java-jar cmdline-jmxclient-0.10 .3.jar-127.0.0.1:1099 java.lang:type=Threading ThreadCount 09/06/2017 12:31:21 +0800 org.archive.jmx.Client ThreadCount: 41# java -jar cmdline-jmxclient-0.10.3 .jar-127.0.0.1:1099 java.lang:type=Threading PeakThreadCount 09/06/2017 12:31:49 +0800 org.archive.jmx.Client PeakThreadCount: 53