You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2013/10/16 01:35:43 UTC

[jira] [Closed] (FELIX-3991) [DS] component deactivation may not complete properly with enough threads

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

David Jencks closed FELIX-3991.
-------------------------------


> [DS] component deactivation may not complete properly with enough threads
> -------------------------------------------------------------------------
>
>                 Key: FELIX-3991
>                 URL: https://issues.apache.org/jira/browse/FELIX-3991
>             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.0
>
>
> I didn't think through the return values from RegistrationManager correctly.  The result was that if a required dependency was removed while service registration was taking place, the deactivation code thought another thread was doing the deactivation and did nothing further.  The dependency managers were then left in an inconsistent state.  For instance a SingleStaticCustomizer was left with the original refPair even though it was removed (the cause of the deactivation).  This would prevent subsequent activation of the component.



--
This message was sent by Atlassian JIRA
(v6.1#6144)