You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2015/10/06 11:12:26 UTC
[jira] [Commented] (OAK-3477) Make JMX Bean names predictable so
they can be used in configurations.
[ https://issues.apache.org/jira/browse/OAK-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944763#comment-14944763 ]
Bertrand Delacretaz commented on OAK-3477:
------------------------------------------
For beans where the name and type might collide, a configurable unique ID suffix might be used to make the name predictable.
> Make JMX Bean names predictable so they can be used in configurations.
> ----------------------------------------------------------------------
>
> Key: OAK-3477
> URL: https://issues.apache.org/jira/browse/OAK-3477
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.3.7
> Reporter: Ian Boston
>
> In Oak there are JMX beans which get names of the form [1], which can be hard to use in monitoring tool configuration that dont support regexes as the ID will change. Where possible, the ID should be removed or made static. The name and type should be sufficient in most cases in Oak to make the JMX Object name unique.
> 1
> {code}
> org.apache.jackrabbit.oak:name="Consolidated Cache
> statistics",type="ConsolidatedCacheStats",id=6
> org.apache.jackrabbit.oak:name="CopyOnRead support
> statistics",type="CopyOnReadStats",id=7
> org.apache.jackrabbit.oak:name="Oak Repository
> Statistics",type="RepositoryStats",id=16
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)