<
From version < 24.1 >
edited by Vincent Massol
on 2014/11/04
To version < 22.3 >
edited by Vincent Massol
on 2014/11/04
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -55,12 +55,8 @@
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 -{{info}}
59 -Note that starting with XWiki 6.3, if you're using the Standalone Distribution (which bundles Jetty) you can now use ##start_xwiki.sh -j## (or ##start_xwiki.sh ~-~-jmx##) to monitor/manage the Jetty instance itself (it adds Jetty-specific MBeans):
58 +Note that starting with XWiki 6.3, if you're using the Standalone Distribution (which bundles Jetty) you can now use ##start_xwiki.sh -j## (or ##start_xwiki.sh ~-~-jmx##) to monitor/manage the Jetty instance itself (it adds Jetty-specific MBeans).
60 60  
61 -{{image reference="jettymbeans.png"/}}
62 -{{/info}}
63 -
64 64  == XWiki Caches Monitoring ==
65 65  
66 66  XWiki can use different cache implementations. The JBoss Cache and JBoss Infinispan implementations have nice JMX features available as shown below.
jettymbeans.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.VincentMassol
Size
... ... @@ -1,1 +1,0 @@
1 -166.8 KB
Content

Get Connected