You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2015/06/18 12:34:00 UTC

[jira] [Assigned] (SLING-4811) Handle OSGi event in a separate thread to prevent being blacklisted by the OSGi Event Admin

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

Konrad Windszus reassigned SLING-4811:
--------------------------------------

    Assignee: Konrad Windszus

> Handle OSGi event in a separate thread to prevent being blacklisted by the OSGi Event Admin
> -------------------------------------------------------------------------------------------
>
>                 Key: SLING-4811
>                 URL: https://issues.apache.org/jira/browse/SLING-4811
>             Project: Sling
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: i18n 2.4.2
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>
> Since Apache Felix blacklists all OSGi Event Handlers which take too long to complete it would be good if all long-running tasks would be executed in a separate thread (like preloading resource bundles).
> Otherwise the {{JcrResourceBundleProvider}} might get blacklisted if the instance is under load and in the future is not notified about any changes. The default timeout of Apache Felix is 5 seconds (http://felix.apache.org/documentation/subprojects/apache-felix-event-admin.html).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)