1 2 Previous Next 16 Replies Latest reply on Nov 11, 2015 9:43 AM by wdfink Go to original post
      • 15. Re: ClusterNodeSelector not being called
        bogdand

        Hi,

        Sorry for the delay.You're right, the cluster selected is invoked from the second call on.

        And the ejb client proxy probably needs to be cached.

        My usecase is as follows:

        I want to be able to remotely invoke the EJB on a master(coordinator) node from any node in the cluster, and for this I need to control the selection of the endpoint node.

        Also, I need to benefit from the auto discovery of the nodes through jgroups/infinispan.

        I hope I can still use the deployment selector though, which is called at every invocation to get this scenario working.

         

        Cheers!

         

        Bogdan

        • 16. Re: ClusterNodeSelector not being called
          wdfink

          There are two different selectors

          DeploymentNodeSelector and ClusterNodeSelector, in case of a cluster you need to use the CNS, the DNS is only called for the first invocation after the proxy has been created.

           

          There is no auto discovery, a cluster node will send the list of nodes in the cluster parallel to the invocation and after that the client create a connection for each and use it.

          1 2 Previous Next