-
Bug
-
Resolution: Done
-
Blocker
-
7.1.0.ER1
-
None
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.
- clones
-
WFLY-9037 Cluster topology updates are lossy
- Closed
- is related to
-
JBEAP-11337 Fix and re-enable RemoteFailoverTestCase
- Closed