Changes for page Monitoring

Last modified by Antoine Mottier on 2023/07/17

<
From version < 21.1 >
edited by Vincent Massol
on 2014/11/03
To version < 22.2 >
edited by Vincent Massol
on 2014/11/03
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -55,6 +55,10 @@
55 55  
56 56  Since JMX is a standard you can use [[any JMX-compatible monitoring console>>http://stackoverflow.com/questions/1744900/what-is-the-best-or-most-commonly-used-jmx-console-client]] (most application servers provide a web-based JMX console). There's also a console called [[JConsole>>http://docs.oracle.com/javase/7/docs/technotes/guides/management/jconsole.html]] which is bundled by default in the Java Runtime you're using. To start it, simply execute the ##jconsole## executable.
57 57  
58 +Note that starting with XWiki 6.3, if you're using the Standalone Distribution (which bundles Jetty) you'll need to start XWiki with ##start_xwiki.sh -j## (or ##start_xwiki.sh ~-~-jmx##) to enable connecting to the Jetty JMX server from outside (for example with ##jconsole##). This parameter has 2 effects:
59 +* It sets ##-Dcom.sun.management.jmxremote##
60 +* It adds some specific Jetty MBeans to monitor/manage the Jetty Server itself
61 +
58 58  == XWiki Caches Monitoring ==
59 59  
60 60  XWiki can use different cache implementations. The JBoss Cache and JBoss Infinispan implementations have nice JMX features available as shown below.

Get Connected