[jira] [Commented] (FELIX-4348) [DS] locateService calls race with component reconfiguration

["David Jencks (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FELIX-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13857881#comment-13857881 ] 

David Jencks commented on FELIX-4348:
-------------------------------------

The first attempted fix causes deadlocks.  The read-write lock cannot extend over service registration/deregistration.  I had a similar deadlock without locateService that was solved in a similar way.

> [DS] locateService calls race with component reconfiguration
> ------------------------------------------------------------
>
>                 Key: FELIX-4348
>                 URL: https://issues.apache.org/jira/browse/FELIX-4348
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>    Affects Versions: scr-1.8.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: scr-1.8.2
>
>
> If a locateService call comes in while a dependency manager is changing it's target filter you get a stack trace like:
> Stack Dump = java.lang.NullPointerException
> 	at org.apache.felix.scr.impl.manager.DependencyManager.getRefPair(DependencyManager.java:1281)
> 	at org.apache.felix.scr.impl.manager.DependencyManager.getService(DependencyManager.java:1299)
> 	at org.apache.felix.scr.impl.manager.ComponentContextImpl.locateService(ComponentContextImpl.java:107)



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)