Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-5572

Exposed JMX MBeans should be separate components

    XMLWordPrintable

Details

    • Task
    • Status: New (View Workflow)
    • Major
    • Resolution: Unresolved
    • 8.0.0.Alpha2, 7.2.3.Final
    • None
    • Core
    • None

    Description

      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).

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              dberinde@redhat.com Dan Berindei
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: