Changes for page Monitoring

Last modified by Antoine Mottier on 2023/07/17

<
From version < 3.2 >
edited by Silvia Macovei
on 2010/06/23
To version < 4.1 >
edited by Vincent Massol
on 2011/05/06
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.SilviaRusu
1 +XWiki.VincentMassol
Content
... ... @@ -2,7 +2,8 @@
2 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 3  * Starting with XWiki Enterprise 2.4M2 we're now 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 4  ** Monitor the Velocity macro caches
5 -** Monitor the caches XWiki is using to cache Document data, Users & Groups data and more
5 +** Monitor the JBossCache caches XWiki is using to cache Document data, Users & Groups data and more
6 +** Monitor the JGroups channel and protocols (when the XWiki Cluster feature is turned on)
6 6  
7 7  {{info}}
8 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.
... ... @@ -12,9 +12,21 @@
12 12  
13 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 14  
15 -Example of JConsole showing the Velocity Cache monitoring:
16 +== Velocity Cache Monitoring ==
16 16  
18 +JConsole examples showing the Velocity Cache monitoring:
19 +
17 17  image:jconsole1.png
18 18  
19 19  image:jconsole2.png
20 20  
24 +== JGroups Monitoring ==
25 +
26 +JConsole example showing the JGroups monitoring:
27 +
28 +image:jgroups.png
29 +
30 +Interesting things to do on JGroups in the JMX console:
31 +* Change the log level on the protocols to enable logging
32 +* Disconnect a node from the cluster and reconnect it
33 +

Get Connected