You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Alex Parvulescu (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/22 23:38:40 UTC
[jira] [Resolved] (JCR-2936) JMX Bindings for Jackrabbit
[ https://issues.apache.org/jira/browse/JCR-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Parvulescu resolved JCR-2936.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.3.4
Marking as resolved. Further dev should follow on its own issue. This one is kinda fat already.
> JMX Bindings for Jackrabbit
> ---------------------------
>
> Key: JCR-2936
> URL: https://issues.apache.org/jira/browse/JCR-2936
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Components: jackrabbit-core
> Reporter: Alex Parvulescu
> Priority: Minor
> Fix For: 2.3.4
>
> Attachments: JCR-2936-part2.patch, JCR-2936.patch
>
>
> There has been a slight interest in the past for adding JMX support.
> This would be the first stab at it. It is a Top 15 slow query log. (the 15 part is configurable)
> It is not enabled by default, so just being there should not affect the overall performance too much. You can enable it and play a little, tell me what you think.
> I've also added a test case that does a duration comparison with and without the logger.
> The most important part of this issue is that it should open the way for some proper monitoring tools support around queries, caches, anything/everything Jackrabbit.
> As usual, please let me know what you guys think
--
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