jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-5594) leaderboard of consolidated listener stats should show path as well
Date Tue, 07 Feb 2017 12:07:41 GMT

    [ https://issues.apache.org/jira/browse/OAK-5594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855855#comment-15855855

Marcel Reutegger commented on OAK-5594:

I would also prefer a solution that reveals the actual listener behind the JcrResourceListener.
One option that comes to my mind is an interface (in Oak or Jackrabbit) that extends EventListener
and adds additional methods. The listener in Sling would implement it and provide information
about the underlying listener.

> leaderboard of consolidated listener stats should show path as well
> -------------------------------------------------------------------
>                 Key: OAK-5594
>                 URL: https://issues.apache.org/jira/browse/OAK-5594
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: jcr
>    Affects Versions: 1.6.0
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>             Fix For: 1.7.0, 1.8
> The consolidated listener stats has a leaderboard section which sorts the leaders by
cumulative processTime. This is useful information, however the className of the listener
does not always allow to identify the culprit. Consider Sling's JcrResourceListener - which
is created for each (group of) ResourceChangeListener. The leaderboard will only show (a number
of) {{JcrResourceListener}} as the className and not which ResourceChangeListener is underneath.
> Ideally each listener could provide more details as to who is 'behind' itself - similarly
to the [EventListenerMBean.getToString|https://github.com/apache/jackrabbit/blob/27dbe3c81c5b6d67c5fa7a50a53e7450218079a2/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/jmx/EventListenerMBean.java#L33].
But atm that sometimes produces rather a lot of output.
> A simpler way might be to just add a column {{paths}} - that would show the same as in
the {{ListenerStats}} table.

This message was sent by Atlassian JIRA

View raw message