Confluence Docs 3.3 : Live Monitoring Using the JMX Interface
This page last changed on Mar 01, 2010 by pwhite.
With the JMX interface (introduced in Confluence 2.8), you can monitor the status of your Confluence instance in real time. This will provide you with useful data such as the resource usage of your instance and its database latency, allowing you to diagnose problems or performance issues. To read the JMX data, you will need to use a JMX client. Disable JMX
What is JMX?JMX (Java Management eXtensions) is a technology for monitoring and managing Java applications. JMX uses objects called MBeans (Managed Beans) to expose data and resources from your application. 1. Enabling JMX Remote with TomcatBy default, Confluence uses the Apache Tomcat web server. To use JMX, you must enable it on your Tomcat server, by carrying out the steps under the Apache Tomcat documentation, entitled Enabling JMX Remote. With those steps completed, restart your Tomcat server. For the stand-alone, add the startup parameter -Dcom.sun.management.jmxremote to setenv.sh or setenv.bat. See instructions for the Windows Service - enter it in the same place as PermGen Memory. 2. Selecting your JMX ClientYou need to use a JMX client in order to view the JMX output from Confluence. JConsole is a readily available JMX client that is included with Sun's Java Developer Kit (version 5 onwards). The full name is the 'Java Monitoring and Management Console', but we will refer to it as JConsole for the purposes of this document. 3. Adding the JMX Client to your PathYou must add the location of the JConsole binary file to your 'path' environment variable. As JConsole resides in the 'bin' (binaries) folder under your Java directory, the path should resemble something like this: JDK_HOME/bin/ In this example, replace 'JDK_HOME' with the full system path to your Java directory. 4. Configuring JConsoleTo configure JConsole,
Note: Other JMX clients besides JConsole can read JMX information from Confluence. What can I monitor with JMX?The JMX interface allows you to see live internal information from your Confluence instance, via the following MBeans: IndexingStatisticsThis MBean shows information related to search indexing.
SystemInformationThis MBean shows information related to database latency. It also contains most of the information presented on the System Information page.
RequestMetricsThis MBean shows information related to system load and error pages served.
MailServer-SMTPServerThis MBean shows information related to email dispatch attempts and failures. There will be an MBean for every SMTP Mailserver that has been configured in the Confluence instance.
MailTaskQueueThis MBean shows information related to the email workload.
SchedulingStatisticsThis MBean shows information related to current jobs, scheduled tasks and the time that they were last run. High CPU consuming threadsFor Java 1.6, add the Top Threads Plugin to monitor whether CPU is spiking. Download it to a directory and run JConsole like this: This works only with jdk 1.6, but that can be on the remote machine if the server is running a lower version. RELATED TOPICS
|
![]() |
Document generated by Confluence on Jul 09, 2010 01:08 |