Chapter 23. Set Up Java Management Extensions (JMX)

Java Management Extension (JMX) is a Java based technology that provides tools to manage and monitor applications, devices, system objects, and service oriented networks. Each of these objects is managed, and monitored by MBeans.

JMX is the de facto standard for middleware management and administration. As a result, JMX is used in Red Hat JBoss Data Grid to expose management and statistical information.

Management in Red Hat JBoss Data Grid instances aims to expose as much relevant statistical information as possible. This information allows administrators to view the state of each instance. While a single installation can comprise of tens or hundreds of such instances, it is essential to expose and present the statistical information for each of them in a clear and concise manner.

In JBoss Data Grid, JMX is used in conjunction with JBoss Operations Network (JON) to expose this information and present it in an orderly and relevant manner to the administrator.

JMX statistics can be enabled at two levels:

You can enable JMX statistics at the Cache level either declaratively or programmatically.

<*-cache statistics="true">

<*-cache statistics="true">

Configuration configuration = new
ConfigurationBuilder().jmxStatistics().enable().build();

Configuration configuration = new
ConfigurationBuilder().jmxStatistics().enable().build();

You can enable JMX statistics at the CacheManager level either declaratively or programmatically.

<cache-container statistics="true">

<cache-container statistics="true">

GlobalConfiguration globalConfiguration = new
GlobalConfigurationBuilder().globalJmxStatistics().enable().build();

GlobalConfiguration globalConfiguration = new
GlobalConfigurationBuilder().globalJmxStatistics().enable().build();

Red Hat JBoss Data Grid allows the CacheStore to be disabled via JMX by invoking the disconnectSource operation on the RollingUpgradeManager MBean.

See Also: RollingUpgradeManager

Multiple JMX domains are used when multiple CacheManager instances exist on a single virtual machine, or if the names of cache instances in different CacheManagers clash.

To resolve this issue, name each CacheManager in manner that allows it to be easily identified and used by monitoring tools such as JMX and JBoss Operations Network.

<globalJmxStatistics enabled="true" cacheManagerName="Hibernate2LC"/>

<globalJmxStatistics enabled="true" cacheManagerName="Hibernate2LC"/>