[
https://issues.apache.org/jira/browse/DERBY-5772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-5772:
---------------------------------
Attachment: derby-5772-db-bean-1.diff
Attaching [^derby-5772-db-bean-1.diff]:
{quote}
adds an mbean per database booted with the following attributes:
getName
getFoo
The first is just the database name (quoted full path). The other is an example
attribute that shows how we could leverage access to the database via SQL in an
MBean if we need it (sans authorization here, though, but I believe we could
extend the bean to cover that). We would probably only want to use a connection
if it might allow some observables that might otherwise be hard or impractical
to extract without SQL. Not sure that is the case, though. Not for commit,
proof of concept only for now.
{quote}
> Give users a way to monitor more Derby internals.
> --------------------------------------------------
>
> Key: DERBY-5772
> URL: https://issues.apache.org/jira/browse/DERBY-5772
> Project: Derby
> Issue Type: Improvement
> Components: JMX, Tools
> Affects Versions: 10.9.1.0
> Reporter: Rick Hillegas
> Attachments: derby-5772-db-bean-1.diff,
> derby-5772-more-pagecache.diff, pagecache-counters.diff,
> pagecache-counters.diff, pagecache-counters.png
>
>
> We should give users a way to track hits/misses in the page cache. This will
> help users tune the size of the page cache. JMX-visible monitors might be a
> useful solution here. See the following email thread:
> http://old.nabble.com/Cache-Hit-Miss-rates-for-Derby-pageCache-to33865646.html#a33865646
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
