3 Replies Latest reply on Aug 13, 2008 12:13 PM by mircea.markus

    cache statistics via JMX

    mircea.markus

      Following information is currently being exposed through JMX:


      1)RpcManager (replCount, replFailuresCount)
      2)ActivationInterceptor (activation count)
      3)CacheLoaderInterceptor (lods, misses)
      4)CacheMngmtInterceptor (hits, missis, puts, eviction count, cache life in secs, avg read/write durration)
      5)InvalidationInterceptor (number of invalidations)
      6)PassivationInterceptor (number of passivations)
      7) Txinterceptor (prepare, commit and rollback count)

      Is there any other information you would find useful for being exposed?
      ( Starting with 3.0 it is much easier to aggregate/expose thorough JMX - JBCACHE-1305 )


        • 1. Re: cache statistics via JMX
          manik

          BuddyManager - current group details (data owner name and buddies) as well as groups the current cache participates in, as a buddy.

          RPCManager - channel information (configuration stack, bound address and port, JGroups View)

          Cache configuration (read-only for non-@Dynamic fields, ability to modify for @Dynamic fields?)

          Eviction queue status - but wait for JBCACHE-1141 for this.

          LockManager - locks currently held? Essentially invoking LockManager.printLockInfo()?



          • 2. Re: cache statistics via JMX
            galder.zamarreno

            Not sure whether this is already included in CacheMngmtInterceptor, but what about read/write percentages?

            What about physical size of cache/regions? (I had someone asking this a short while back)

            • 3. Re: cache statistics via JMX
              mircea.markus

               

              Not sure whether this is already included in CacheMngmtInterceptor, but what about read/write percentages?

              not exposed yet, good point
              What about physical size of cache/regions? (I had someone asking this a short while back)

              +1
              we need to implement https://jira.jboss.org/jira/browse/JBCACHE-11 before being able to expose that one