jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Parvulescu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCR-2936) JMX Bindings for Jackrabbit
Date Thu, 14 Apr 2011 11:59:05 GMT

     [ https://issues.apache.org/jira/browse/JCR-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alex Parvulescu updated JCR-2936:
---------------------------------

    Attachment: JCR-2936-part2.patch

apparently when running multiple tests on the repository, the jmx bean registration fails
in the initialization part.

it may have something to do with the way the test repo is setup, but either way, it fails
constantly

I'm attaching a patch that fixes this problem.

For the design improvements, I'm still planning it out :)

> 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

Mime
View raw message