[
https://issues.apache.org/jira/browse/JCR-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Parvulescu updated JCR-3186:
---------------------------------
Attachment: JCR-3186.patch
I'm trying out a different approach.
Let's see how it looks like if the ObservationDispatcher maintains and exposes
its own stat object.
To be able to maintain the stats object up to date it will need an executor.
I've added a new constructor so we can pass in the repository's central
executor for the updates.
For now, no executor means no stats update. We may need to reconsider this in
the future if it proves not sufficient enough.
attached proposed patch.
> Export size of Observation eventQueue to JMX
> --------------------------------------------
>
> Key: JCR-3186
> URL: https://issues.apache.org/jira/browse/JCR-3186
> Project: Jackrabbit Content Repository
> Issue Type: Wish
> Components: jackrabbit-core
> Reporter: Jörg Hoh
> Priority: Minor
> Attachments: JCR-3186.patch, JR-observationQueueJMX-trunk.patch
>
>
> export the size of the event queue of JCR Observation to JMX.
--
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
