You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2011/09/11 22:54:09 UTC
[jira] [Updated] (JCR-2936) JMX Bindings for Jackrabbit
[ https://issues.apache.org/jira/browse/JCR-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-2936:
-------------------------------
Comment: was deleted
(was: Dear sender,
I'm currently out of the office and will not be able to read my email.
For urgent Hippo matters please send an email to helpdesk@onehippo.com
or call: +31205224466
Kind regards,
Jeroen Reijn
Hippo
--
Amsterdam - Oosteinde 11, 1017 WT Amsterdam
Boston - 1 Broadway, Cambridge, MA 02142
US +1 877 414 4776 (toll free)
Europe +31(0)20 522 4466
www.onehippo.com
)
> 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
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira