Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-9037

Cluster topology updates are lossy

    Details

      Description

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  pferraro Paul Ferraro
                  Reporter:
                  dmlloyd David Lloyd
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: