[
https://issues.apache.org/jira/browse/SLING-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-911.
-----------------------------------
Tests seem to indicate this issue is really fixed. So closing this issue now.
> ResourceProvider registration issues: better info on duplicate, prevent loss
> on registration
> --------------------------------------------------------------------------------------------
>
> Key: SLING-911
> URL: https://issues.apache.org/jira/browse/SLING-911
> Project: Sling
> Issue Type: Bug
> Components: JCR Resource
> Affects Versions: JCR Resource 2.0.4
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR Resource 2.0.4
>
>
> The resource provider registration and unregistration has some issues
> currently:
> * Multi-threading: ResourceProvider may be registered and/or unregistered at
> any time. Currently the handling of this registration or unregistration is
> not done in a thread safe way. Therefore it may happen that some
> registrations are lost or that some unregistrations are actually lost and do
> not take place.
> * If a resource provider is registered for a path for which a registered
> provider already exists, there is currently no information on the existing
> resource provider.
> This bug is about fixing these issues by synchronizing on provider
> registration and unregistration and by providing a hint to the resource
> provider in the log message on duplicate registrations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
