You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/02/02 09:08:35 UTC

[jira] [Closed] (SLING-4361) Improve handling of unregistering ResourceProviderFactories

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

Carsten Ziegeler closed SLING-4361.
-----------------------------------

> 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)