David Lloyd created WFLY-9037: --------------------------------- Summary: Cluster topology updates are lossy Key: WFLY-9037 URL: https://issues.jboss.org/browse/WFLY-9037 Project: WildFly Issue Type: Bug Components: Clustering Reporter: David Lloyd Assignee: Paul Ferraro Priority: Blocker Fix For: 11.0.0.Beta1 EJB code is not getting a complete cluster topology. In AssociationImpl, we register cluster topology listeners by adding a {{RegistryCollector.Listener<String, List<ClientMapping>>}}. Because this listener will only receive updates relative to the time it was registered, we also iterate all the values of the original {{RegistryCollector<String, List<ClientMapping>>}} by using its {{getRegistries()}} method at this time. However, this iteration always seems to come up empty, or else we're missing notifications some other way. So we end up with an incomplete cluster view and client invocations fail because of a perceived lack of node availability. -- This message was sent by Atlassian JIRA (v7.2.3#72005)