[
https://issues.apache.org/jira/browse/FELIX-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated FELIX-4538:
------------------------------------
Fix Version/s: (was: scr-2.0.2)
scr-2.0.4
> [DS] problem with stale references with "triangle" of static references
> -----------------------------------------------------------------------
>
> Key: FELIX-4538
> URL: https://issues.apache.org/jira/browse/FELIX-4538
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Affects Versions: scr-1.8.2
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: scr-2.0.4
>
>
> Lets say you have a service A and DS components B and C, each with a static
> reference to A, and that C also has a static reference to B. Suppose B and C
> are immediate or there is some other reason C will be recreated immediately.
> If everything is running, and you unregister A, a service event goes out
> announcing this.
> If B gets the event first, it will deactivate and activate immediately. This
> causes C to deactivate and reactivate. However C's service tracker for A has
> not yet received the notification that A is gone and with current code C will
> be created with a stale reference to A. (in a moment C is notified that A is
> gone and gets recreated again)
> If C gets the event first, there won't be this problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
