Monitoring with JMX

The CMS Server can expose attributes from JMX beans over http in JSON format for monitoring purposes.

1 Configuration

1.1 Access Control

By default, accessing the monitoring data is secured and is only possible from localhost.


      secured: true
      allowedfrom: ", ::1"
Property name Description
accesscontrol.jmx.secured true to secure access, false to disable security
accesscontrol.jmx.allowedfrom list of IP addresses that can access monitoring data

Generally, it is not recommended to disable security for the monitoring data.

1.2 JMX Beans

The exposed JMX beans can be defined in the configuration files (the following list contains the beans, that are exposed by default):


    - HeapMemoryUsage
    - NonHeapMemoryUsage
    - ObjectPendingFinalizationCount
  'java.lang:type=Threading': "*"
  'java.lang:type=OperatingSystem': "*"
  'com.gentics.contentnode.mbeans:type=Publish,name=PublisherInfo': "*"
  'com.gentics.contentnode.mbeans:type=System,name=SessionInfo': "*"
  'com.gentics.contentnode.mbeans:type=System,name=TrxInfo': "*"
  'Catalina:type=GlobalRequestProcessor,name="ajp-nio-8009"': "*"
  'Catalina:type=Manager,host=localhost,context=/': "*"
  'org.glassfish.jersey:type=GCMS,subType=Global,executionTimes=AllRequestTimes': "*"

The key must be the full name of the JMX bean, the value may be an array of exposed attributes, or "*" to expose all attributes.

2 Accessing JMX beans

The exposed JMX beans can be accessed over an http GET request to http://[hostname]/jmx.

The response will contain the monitoring data in JSON format.