Eclipse/jetty.project
1
0
Fork 0
mirror of https://github.com/jetty/jetty.project.git synced 2025-02-24 08:28:54 +00:00
Code Issues Packages Projects Releases Wiki Activity
jetty.project/jetty-monitor
History
Simone Bordet 347c48d657 Revert "resolve merge and update license headers" 
This reverts commit 53b31b03ddda3776f3db71e28e55312b1c982092, reversing
changes made to 4565c186d7491a97d72217a96e86b15ced506de6.
2017-01-19 18:26:43 +01:00
..
src
Revert "resolve merge and update license headers"
2017-01-19 18:26:43 +01:00
pom.xml
Updating to version 9.3.16-SNAPSHOT
2016-12-20 13:09:32 -07:00
README.TXT
renamed README.txt to README.TXT and updated contents
2013-08-29 00:32:36 +10:00

README.TXT 

The ThreadMonitor is distributed as part of the jetty-monitor module. 

In order to start ThreadMonitor when server starts up, the following command line should be used.

    java -jar start.jar OPTIONS=monitor jetty-monitor.xml

To run ThreadMonitor on a Jetty installation that doesn't include jetty-monitor module, the jetty-monitor-[version].jar file needs to be copied into ${jetty.home}/lib/ext directory, and jetty-monitor.xml configuration file needs to be copied into ${jetty.home}/etc directory. Subsequently, the following command line should be used.

    java -jar start.jar etc/jetty-monitor.xml

If running Jetty on Java VM version 1.5, the -Dcom.sun.management.jmxremote option should be added to the command lines above in order to enable the JMX agent.

In order to log CPU utilization for threads that are above specified threshold, you need to follow instructions inside jetty-monitor.xml configuration file.