[
https://issues.apache.org/jira/browse/DERBY-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14732108#comment-14732108
]
Bryan Pendleton commented on DERBY-6733:
----------------------------------------
I was able to access all three of these beans using JConsole without problems.
It took me a little while to figure out that HitCount and MissCount and
EvictionCount
weren't ever going to be non-zero unless I set CollectAccessCounts to true.
Probably we will want to improve the documentation, over time, to describe
how to use the bean information effectively to monitor a Derby system.
Perhaps we could also put some amount of documentation into the bean
attribute descriptions themselves? In JConsole, the bean attribute descriptions
all simply read "Attribute exposed for management"; is that text that we
provided
or is that automatically generated by JConsole?
> 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
> Fix For: 10.12.0.0
>
> Attachments: d6733-1a-page-and-container.diff,
> d6733-2a-statement-cache.diff, d6733-3a-adminguide.diff,
> d6733-4a-test-permissions.diff, radminjmxintro.html
>
>
> 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)
