[jboss-jira] [JBoss JIRA] (WFLY-7765) Application deployed as "singleton-deployment" in a cluster is not reachable for EJB calls under all circumstances

[Wolf-Dieter Fink (JIRA)]

Wolf-Dieter Fink created WFLY-7765:
--------------------------------------

             Summary: Application deployed as "singleton-deployment" in a cluster is not reachable for EJB calls under all circumstances
                 Key: WFLY-7765
                 URL: https://issues.jboss.org/browse/WFLY-7765
             Project: WildFly
          Issue Type: Bug
          Components: EJB
            Reporter: Wolf-Dieter Fink




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.





--
This message was sent by Atlassian JIRA
(v7.2.3#72005)