sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SLING-6943) Don't call into service registry from within a synchronized block
Date Fri, 24 Nov 2017 07:16:00 GMT

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

Carsten Ziegeler resolved SLING-6943.
-------------------------------------
    Resolution: Fixed
      Assignee: Carsten Ziegeler

Applied the patch in rev f2f1bc2

> Don't call into service registry from within a synchronized block
> -----------------------------------------------------------------
>
>                 Key: SLING-6943
>                 URL: https://issues.apache.org/jira/browse/SLING-6943
>             Project: Sling
>          Issue Type: Improvement
>          Components: ResourceResolver
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Resource Resolver 1.5.32
>
>         Attachments: SLING-6943.patch
>
>
> ResourceProviderTracker activates and deactivates resource providers within a synchronized
block which then calls get/unget service on the service registry.
> I think we should avoid doing these calls within a sync'ed block



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message