Managed Beans available through JMX
This topic has not yet been written. The content below is from the topic description.
Understanding The MBeans Once you have enabled JMX reporting at either the CacheManager or Cache level, you should be able to connect to VM(s) where Infinispan is running using a standard JMX GUI such as JConsole or VisualVM, and you should find the following MBeans: Infinispan 4.1 or earlier If you enabled CacheManager level JMX statistics, you should see an MBean called infinispan:cache-name=[global],jmx-resource=CacheManager with properties specified by the CacheManager MBean. If you enabled Cache level JMX statistics, you should see several different MBeans depending on which configuration options have been enabled. For example, if you have configured a write behind cache store, you should see an MBean exposing properties belonging to the cache store component. All Cache level MBeans will follow the same format though which is the following: infinispan:cache-name= (),jmx-resource= where: has been substituted by the actual cache name. If this cache represents the default cache, its name will be "___defaultcache". has been substituted by the cache mode of the cache. The cache mode is represented by the lower case version of the possible enumeration values shown here. has been substituted by one of the JMX component names in the JMX reference documentation.  For example, the cache store JMX component MBean for a default cache configured with synchronous distribution would have the following name:infinispan:cache-name=___defaultcache(dist_sync),jmx-resource=CacheStore  Please note that any cache names that contain ':' or '=' characters will be substituted by '_' character. Infinispan does this because ':' and '=' are control characters for JMX object names. Infinispan 4.2 or later If you enabled CacheManager level JMX statistics, without further configuration, you should see an MBean called org.infinispan:type=CacheManager,name="DefaultCacheManager" with properties specified by the CacheManager MBean. Using the cacheManagerName attribute in globalJmxStatistics XML element, or using the corresponding GlobalConfiguration.setCacheManagerName() call, you can name the cache manager in such way that the name is used as part of the JMX object name. So, if the name had been "Hibernate2LC", the JMX name for the cache manager would have been: org.infinispan:type=CacheManager,name="Hibernate2LC". This offers a nice and clean way to manage environments where multiple cache managers are deployed, which follows JMX best practices. If you enabled Cache level JMX statistics, you should see several different MBeans depending on which configuration options have been enabled. For example, if you have configured a write behind cache store, you should see an MBean exposing properties belonging to the cache store component. All Cache level MBeans follow the same format though which is the following: org.infinispan:type=Cache,name="()",manager="",component= where: has been substituted by the actual cache name. If this cache represents the default cache, it's name will be "___defaultCache". has been substituted by the cache mode of the cache. The cache mode is represented by the lower case version of the possible enumeration values shown here. has been substituted by the name of the cache manager to which this cache belongs. The name is derived from the cacheManagerName attribute value in globalJmxStatistics element. has been substituted by one of the JMX component names in the JMX reference documentation.  For example, the cache store JMX component MBean for a default cache configured with synchronous distribution would have the following name: org.infinispan:type=Cache,name="___defaultcache(dist_sync)", manager="DefaultCacheManager",component=CacheStore  Please note that cache and cache manager names are quoted to protect against illegal characters being used in these user-defined names.