[infinispan-issues] [JBoss JIRA] (ISPN-2371) The global component registry sometimes fails to start components injected on the fly

[Tristan Tarrant (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749179#comment-12749179 ] 

Tristan Tarrant commented on ISPN-2371:
---------------------------------------

Closed this issue and created a clone for the proper fix at ISPN-2735
                
> The global component registry sometimes fails to start components injected on the fly
> -------------------------------------------------------------------------------------
>
>                 Key: ISPN-2371
>                 URL: https://issues.jboss.org/browse/ISPN-2371
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Locking and Concurrency
>    Affects Versions: 5.2.0.Beta1
>            Reporter: Dan Berindei
>            Assignee: Dan Berindei
>             Fix For: 5.2.0.Final
>
>
> If a global component is used by an incoming command, it could be created before the component registry is in the "running" state, yet after it has started invoking the components' start methods.
> If this happens, the component's start method(s) will never be invoked - neither "inline", in ACR.registerComponentInternal, nor in the regular startup procedure (ACR.internalStart).
> Specifically, the problem ocurred with LocalTopologyManager, which is injected in incoming CacheTopologyControlCommands. Since these commands are broadcasted to the entire cluster, a node can receive them before it had finished starting its global component registry.

--
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