You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2013/11/07 09:08:19 UTC

[jira] [Resolved] (OAK-1084) Allow blacklisting of rogue observation listener

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

Chetan Mehrotra resolved OAK-1084.
----------------------------------

    Resolution: Fixed

Resolving as per above comments

> Allow blacklisting of rogue observation listener
> ------------------------------------------------
>
>                 Key: OAK-1084
>                 URL: https://issues.apache.org/jira/browse/OAK-1084
>             Project: Jackrabbit Oak
>          Issue Type: Wish
>          Components: jcr
>            Reporter: Chetan Mehrotra
>            Priority: Minor
>
> Currently Oak dispatches the observation events through a single thread. As best practice its recommended that ObservationListener should not block the main event thread and instead process the event asynchronously in separate thread.
> However it can happen that some rogue implementation does not adhere to this best practice and blocks the main event thread. It would be helpful to have some support in Oak 
> # To identify such listeners which take more time then a defined interval
> #  Blacklist such listeners from further event processing and log a warning about the same
> This feature would be similar to one supported by Felix EventAdmin [1] where EventHandlers are blacklisted in case they timeout
> [1] http://felix.apache.org/site/apache-felix-event-admin.html#ApacheFelixEventAdmin-Configuration



--
This message was sent by Atlassian JIRA
(v6.1#6144)