[jboss-jira] [JBoss JIRA] (WFLY-2674) Criteria for triggering @TopologyChanged logic in RegistryFactoryService is wrong

[Jason Greene (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Greene updated WFLY-2674:
-------------------------------

    Fix Version/s: 8.0.0.Final
                       (was: 8.0.0.CR1)

    
> Criteria for triggering @TopologyChanged logic in RegistryFactoryService is wrong
> ---------------------------------------------------------------------------------
>
>                 Key: WFLY-2674
>                 URL: https://issues.jboss.org/browse/WFLY-2674
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: 8.0.0.Beta1
>            Reporter: Paul Ferraro
>            Assignee: Paul Ferraro
>            Priority: Critical
>             Fix For: 8.0.0.Final
>
>
> There are 2 issues:
> 1. In the fast-fail criteria:
> if (event.isPre() && event.getCache().getCacheManager().isCoordinator()) return;
> This should be an OR not an AND.
> 2. The channel coordinator may not have this registry service running!  Determine the "coordinator" based on the value of event.getConsistentHashAtEnd().
> This is bug is probably the root cause for a number of a large number of transient failures in the clustering testsuite.

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