Uploaded image for project: 'EJB Client Library (AS7+)'
  1. EJB Client Library (AS7+)
  2. EJBCLIENT-110

ClusterContext does not check managed nodes when adding ClusterNodeManagers

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 2.1.0.Final
    • Fix Version/s: 2.1.0.Final
    • Labels:
      None

      Description

      In order to process cluster topology updates, ClusterContext has a method called addClusterNodes(ClusterNodeManager ...) which is used to add ClusterNodeManagers to the ClusterContext. Each added ClusterNodeManager represents a cluster node and an EJBReceiver which can be used to connect to it.

      Because of the fact that, for every change in the cluster topology, a client may receive multiple cluster topology updates (one from each surviving member), the ClusterContext will receive multiple addition requests for the same nodes.

      ClusterContext.addClusterNodes(ClusterNodeManager ...) does not check whether a node is currently managed or not before updating the managedNodes map, which maps nodes to their ClusterNodeManager instances. This overwriting of map entries is unnecessary and probably creates problems downstream.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  dmlloyd David Lloyd
                  Reporter:
                  rachmato Richard Achmatowicz
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: