[
https://issues.apache.org/jira/browse/JCR-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13221035#comment-13221035
]
Alex Parvulescu commented on JCR-3186:
--------------------------------------
It is interesting that we already have the counter info, and it would be
extremely simple to turn that into a counter managed by the
RepositoryStatistics, which in turn can qualify it as an exposed statistic.
This implies that we have to find a way to get the RepositoryStatistics object
from the ObservationDispatcher.
One way is to change the default constructor to take the RepositoryContext as a
param:
public ObservationDispatcher() would become
public ObservationDispatcher(RepositoryContext rc)
Or add another constructor (besides the default one) that takes the
RepositoryContext as a param. This would make the difference between a managed
counter and a simple AtomicLong for the queue size.
I see no cleaner way of getting the RepositoryStatistics object from the
ObservationDispatcher.
thoughts?
> 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: 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
