[ 
https://issues.apache.org/jira/browse/DERBY-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Knut Anders Hatlen updated DERBY-6733:
--------------------------------------
    Attachment: d6733-1a-page-and-container.diff

Attaching [^d6733-1a-page-and-container.diff] which is a refinement of the 
experimental patches attached to DERBY-5772. It adds a new MBean called 
CacheManagerMBean, and creates instances of it for the page cache and the 
container cache when a database is booted.

The MBean has the following attributes:
- CollectAccessCounts (boolean, read/write): tells the MBean whether or not all 
cache accesses should be counted (default is off)
- HitCount (long, read-only): number of cache hits counted
- MissCount (long, read-only): number of cache misses counted
- EvictionCount (long, read-only): number of evictions from the cache
- MaxEntries (long, read-only): the maximum capacity of the cache
- AllocatedEntries (long, read-only): the number of entries in the cache (this 
number includes objects that have been removed from the cache, but whose 
entries have not been reused by other objects yet)
- UsedEntries (long, read-only): the number of entries in the cache that 
actually correspond to a valid object

The patch also adds a new regression test (CacheManagerMBeanTest) with basic 
functional tests for the new MBean.

All regression tests passed with the patch.

> Implement an MBean for monitoring caches
> ----------------------------------------
>
>                 Key: DERBY-6733
>                 URL: https://issues.apache.org/jira/browse/DERBY-6733
>             Project: Derby
>          Issue Type: Improvement
>          Components: JMX
>    Affects Versions: 10.12.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>         Attachments: d6733-1a-page-and-container.diff
>
>
> Add an MBean that allows users to monitor Derby's CacheFactory instances, as 
> discussed in DERBY-5772.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to