[ https://issues.apache.org/jira/browse/SLING-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645651#comment-14645651 ]
Marius Petria commented on SLING-4895: -------------------------------------- [~cziegeler] that is exactly the "concurrency fix". As updateServiceMappings is no longer synchronized, it can happen that two threads pass the guard an register a service for the same mapping, but in that case one needs to unregister one of the services. > Service registry should not be called from within synchronized block > -------------------------------------------------------------------- > > Key: SLING-4895 > URL: https://issues.apache.org/jira/browse/SLING-4895 > Project: Sling > Issue Type: Bug > Components: Extensions > Affects Versions: Service User Mapper 1.2.0 > Reporter: Carsten Ziegeler > Fix For: Service User Mapper 1.2.2 > > Attachments: SLING-4895.diff > > > RIght now, if e.g. an amendment is added/removed/updated, all > registration/unregistration is done in a "large" synchronized block. This > should be avoided -- This message was sent by Atlassian JIRA (v6.3.4#6332)