[jira] [Commented] (FELIX-4538) [DS] problem with stale references with "triangle" of static references

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

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

David Jencks commented on FELIX-4538:
-------------------------------------

After some discussion, this should not be a problematical situation at all, although it ought to be quite temporary.  I will try to recreate the original situation to see if there is any indication DS is behaving badly.

> [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.0
>
>
> 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)