felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FELIX-3991) [DS] component deactivation may not complete properly with enough threads
Date Sun, 24 Mar 2013 06:13:15 GMT

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

David Jencks resolved FELIX-3991.

    Resolution: Fixed

Fixed in rev 1460261.  I added quite a bit of logging until I understood where the problem
was.  Fixed, javadoced, and logged the RegistrationManager return values.  I also did a bit
of method renaming and log clarification.

> [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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message