Eclipse
/
jetty.project
mirror of https://github.com/jetty/jetty.project.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
jetty.project/jetty-monitor
History
Simone Bordet 599ab9bb1b 460671 - Rationalize property names. 
Property format is now "jetty.<module|component>.<propertyName>".

Updated all references with new properties.
 		2015-04-13 16:21:48 +02:00
..
src 460671 - Rationalize property names. 2015-04-13 16:21:48 +02:00
README.TXT renamed README.txt to README.TXT and updated contents 2013-08-29 00:32:36 +10:00
pom.xml [maven-release-plugin] prepare for next development iteration 2014-12-05 16:45:12 +01: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.