[
https://issues.apache.org/jira/browse/SLING-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605276#comment-14605276
]
Konrad Windszus commented on SLING-4811:
----------------------------------------
[~alexander.klimetschek] Thanks for your comments. I made the delay
configurable in rev. 1688114 and also disabled the delay for the initial
preloading of the cache.
In general the delay only affects the invalidation and preloading (if enabled).
If a request comes in before the delay has timed out, this will not defer the
request, but rather just use the resource bundle from the cache (if it already
cached) or load it immediately (without a delay).
> 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
> Fix For: i18n 2.4.4
>
> Attachments: SLING-4811-v02.patch
>
>
> 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)
