[infinispan-issues] [JBoss JIRA] (ISPN-5572) Exposed JMX MBeans should be separate components
Dan Berindei (JIRA)
issues at jboss.org
Wed Jun 24 02:40:04 EDT 2015
Dan Berindei created ISPN-5572:
----------------------------------
Summary: Exposed JMX MBeans should be separate components
Key: ISPN-5572
URL: https://issues.jboss.org/browse/ISPN-5572
Project: Infinispan
Issue Type: Task
Components: Core
Affects Versions: 7.2.3.Final, 8.0.0.Alpha2
Reporter: Dan Berindei
Fix For: 8.0.0.Final
We currently expose internal components as JMX MBeans, and that makes our JMX "API" very unstructured. The exposed MBeans should be separate components, and the only concern in their interfaces should be ease of use.
One example of JMX getting in the way of refactoring is {{CacheMgmtInterceptor}}. The interceptor chain is dynamic, so it should be possible to insert the interceptor only when statistics are enabled. But because the {{statisticsEnabled}} attribute is on the interceptor itself, that becomes a lot trickier, and we had to introduce a separate configuration attribute that disables statistics permanently (ISPN-5542).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the infinispan-issues
mailing list