Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-7542

Application deployed as "singleton-deployment" in a cluster is not always reachable for EJB calls

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • 7.1.0.DR18
    • Clustering, EJB
    • Workaround Exists
    • Hide

      As a workaround all nodes can be added to the client side

      Show
      As a workaround all nodes can be added to the client side
    • Hide

      Use the example:
      https://github.com/wfink/jboss-eap-playground/tree/master/eap7ClusterHASingletonDeployment

      The client try to invoke the node without port-offset. If the nodes are started in different order, or the node1 is brought down during runtime the EJB invocations are failing.

      Show
      Use the example: https://github.com/wfink/jboss-eap-playground/tree/master/eap7ClusterHASingletonDeployment The client try to invoke the node without port-offset. If the nodes are started in different order, or the node1 is brought down during runtime the EJB invocations are failing.

      If an application (singleton-deployment) is deployed into a cluster with more nodes than are initial in the list of the client it can happen that a node is elected to run this application which is not know initially by the client,
      or
      the node with the singleton application is shutted down or crash during runtime.

      In any case the EJB invocation will not work if a node is elected to run the deployment which is not part of the servers listed as initial connections at client side.

      With some BYTEMAN rules I checked that the client side ClusterTopologyMessageHandler and ClusterNodeRemovalHandler did not see more than the node which have the application deployed.
      If all nodes are added to the client jboss-ejb-client.properties the DeploymentNodeSelector is used for the first invocation, the cluster-view is received with one node.
      After this node is down the DNS will show another node and the cluster-view received afterwards onyl show this node.

            Unassigned Unassigned
            rhn-support-wfink Wolf Fink
            Michal Vinkler Michal Vinkler
            Michal Vinkler Michal Vinkler
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: