Collecting data for performance issues using JMX statistics

Merative ™ Social Program Management is now Cúram ™ by Merative™

Collecting data for Merative ™ Social Program Management performance issues using JMX statistics

Question & Answer

Question

How do you collect JMX Statistics in Merative Social Program Management? Collecting Merative Social Program Management JMX statistics before calling Merative support will help clarify the problem and save time analyzing the data.

Answer

Merative Social Program Management JMX performance files should be provided for all relevant application server or batch environments. For more information about Merative Social Program Management JMX statistics, see the Configuring Merative Social Program Management JMX topic of the documentation.

Due to its low overhead and value in giving visibility to Merative Social Program Management performance data, it is recommended that JMX statistics are always enabled and monitored in production environments.

Considerations for Running Merative Social Program Management JMX Statistics

In terms of performance overhead, the only JMX feature that can have a significant impact on certain systems is JMX Transaction Tracing. Transaction tracing is off by default and should be used only when investigating issues, and only for a short period. It is controlled by the curam.jmx.transaction_tracing_enabled property.

Merative SPM JMX Statistics Setup and Access

See the Access to the JMX Statistics topic in the documentation for details on how to set up and access JMX statistics in the Merative Social Program Management application.

With multiple environments or timeframes, when downloading statistics via a browser it is suggested that you name or store the output zip files so they can later be processed or associated with other related artifacts.
If you are gathering JMX statistics for a specific repeatable scenario it can be useful to reset the statistics before rerunning the scenario so the values are more representative.
Reset statistics by using the URL: Curam/JMXStats.do?action=reset

Verifying JMX Statistics

Incorrect configuration can cause JMX statistics to be incomplete. You can do the following for any JMX statistics file and be confident that any others created in the same context are valid:

1. The JMX statistics XML file is densely formatted and not very human-readable. Use the following sample Ant build script to convert all XML files in the current directory to HTML, which is a more user-friendly format:
   
   <?xml version="1.0" encoding="UTF-8"?>
   <project name="JmxToHtml" default="go">
   
   <target name="go" description="Formats JMX files into HTML documents.">
   <xslt destdir="." excludes="build.xml" style="JMXStats.xsl">
   <mapper type="glob" from="*.xml" to="*.html"/>
   </xslt>
   </target>
   </project>
   
   

2. Search for the BPOMethodStats table and ensure it has content. (Not to be confused with the InFlightBPOMethodStats table, which might be empty if there is no in-flight activity when the statistics were generated).

3. If there is no BPOMethodStats data, review the Configuring Merative Social Program Management JMX topic in the documentation, update your configuration (which may require an application server restart), re-gather the statistics, re-validate the statistics, and submit them with your PMR.

Timer-Based JMX Statistics

Merative Social Program Management JMX statistics can be configured to run on a timed basis; for example, once per hour. Setting up timer-based statistics involves passing Java properties on the JVM invocation of either the application server or the batch process.

The following table describes the Merative Social Program Management JMX timer properties: