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 2017/03/29 13:38:41 UTC
[jira] [Updated] (SLING-4944) JcrResourceBundleProvider: Potential
race condition between setting the resourceResolver and using it
[ https://issues.apache.org/jira/browse/SLING-4944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated SLING-4944:
-----------------------------------
Component/s: i18n
> JcrResourceBundleProvider: Potential race condition between setting the resourceResolver and using it
> -----------------------------------------------------------------------------------------------------
>
> Key: SLING-4944
> URL: https://issues.apache.org/jira/browse/SLING-4944
> Project: Sling
> Issue Type: Bug
> Components: Extensions, i18n
> Affects Versions: i18n 2.4.4
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Fix For: i18n 2.4.6
>
>
> After fixing SLING-4910 there is still a very slim chance that the resource resolver is being null while being used within the scheduleReloadBundles, because that is called, before the resolver is initialized. The chance to see that in reality is close to zero though, because scheduleReloadBundles is using the resource resolver only in a scheduled thread.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)