[
https://issues.apache.org/jira/browse/JCR-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124899#comment-13124899
]
Jukka Zitting commented on JCR-3040:
------------------------------------
I'm not aware of any best practices beyond the basic JMX documentation, so for
now I'd prefer to avoid having too many JMX dependencies inside Jackrabbit
core. Ideally the repository itself would just collect all the interesting
information and a deployment could then decide whether to make that information
available through JMX.
The ways of making such information available should be flexible enough to
allow for new bits to be exposed even without changing the APIs.
> JMX Stats for the Session
> -------------------------
>
> Key: JCR-3040
> URL: https://issues.apache.org/jira/browse/JCR-3040
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Components: jackrabbit-core
> Reporter: Alex Parvulescu
> Assignee: Alex Parvulescu
> Attachments: JCR-3040-v2.patch, JCR-3040.patch, jr-test.log
>
>
> I've named them Core stats. This will include:
> - number of sessions currently opened
> - session read / write operations per second
> The stats refresh once a minute.
> This is disabled by default, so it will not affect performance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
