jetty.project/jetty-monitor
Greg Wilkins 30bab30d9b Revert "Merge branch 'release-8' into jetty-8"
This reverts commit 463ef68dc3, reversing
changes made to de544ddfbf.
2013-09-16 23:28:59 +10:00
..
src 416990 JMX names statically unique 2013-09-12 12:29:24 +10:00
README.txt 352684 Implemented logging of thread CPU utilisation in Thread Monitor 2011-08-02 20:59:12 -04:00
pom.xml Revert "Merge branch 'release-8' into jetty-8" 2013-09-16 23:28:59 +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.