Wiki source code of Monitoring
Version 2.3 by Vincent Massol on 2010/06/23
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | There are 2 solutions you can use to monitor a running XWiki instance: | ||
2 | * [[Use a Profiler>>http://dev.xwiki.org/xwiki/bin/view/Community/Profiling]]. This has the advantage of providing advanced information but has the drawback of being resource intensive and thus slowing the XWiki instance. It also requires a special startupscript | ||
3 | * Starting with XWiki Enterprise 2.4M2 we've now started using the [[JMX Technology>>http://en.wikipedia.org/wiki/Java_Management_Extensions]] to provide runtime monitoring of XWiki instances. The following features are currently available: | ||
4 | ** Monitor the Velocity macro caches | ||
5 | ** Monitor the caches XWiki is using to cache Document data, Users & Groups data and more | ||
6 | |||
7 | {{info}} | ||
8 | XWiki also has a [[Monitor Plugin>>platform:AdminGuide.Logging#HActivatingtheXWikimonitoringfeature]] that you can use to monitor execution times. However this plugin is going to be deprecated in the future and replaced by the JMX technology. | ||
9 | {{/info}} | ||
10 | |||
11 | = JMX Console = | ||
12 | |||
13 | 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 such a console called [[JConsole>>http://java.sun.com/developer/technicalArticles/J2SE/jconsole.html]] and which is bundled by default in the Java Runtime you're using. To start it, simply execute the ##jconsole## executable. | ||
14 | |||
15 | Example of JConsole showing the Velocity Cache monitoring: | ||
16 | |||
17 | image:jconsole1.png | ||
18 | |||
19 | image:jconsole2.png |