[
https://issues.apache.org/jira/browse/SLING-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-4361.
-------------------------------------
Resolution: Fixed
I've refactored the handling in 1655358 to use a background thread for
coordination. When an unregistration happens, the reregistration is delayed for
2 secs
> Improve handling of unregistering ResourceProviderFactories
> -----------------------------------------------------------
>
> Key: SLING-4361
> URL: https://issues.apache.org/jira/browse/SLING-4361
> Project: Sling
> Issue Type: Improvement
> Components: ResourceResolver
> Affects Versions: Resource Resolver 1.1.10
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Resource Resolver 1.1.12
>
>
> Right now, if a ResourceProviderFactory is unregistered, the
> ResourceResolverFactory is first unregistered and then registered again. This
> is in order to clean up all usages of ResourceResolvers which might have a
> reference to the unregistered provider factory.
> This reregistration can lead to nearly the whole system going down and up
> again. Therefore if there are several unregistrations in a row, the system
> might go down and up several times. If there are circular dependencies, this
> might also result in an endless down/up loop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
