I am trying to understand how clustering works with JBOSS 7.1
As per the JBOSS documentation I have read...Remote client can have any one server entry into jboss-ejb-client.properties....from the list of cluster instances.But it is not working....Could someone please take a look at it.
Here is my configuration, When I bring down the server instance 1(4447) , then I can not send request to instace 2 anymore...I get this exception (Exception in thread "main" java.lang.IllegalStateException: No EJB receiver available for handling [appName:,modulename:sample,distinctname:])
On the server I have @Clustered / @Stateless simple java bean
Server Instance 1 :
----------------------------
standalone.bat -server-config=standalone-ha.xml -Djboss.server.base.dir=instance1 -Djboss.node.name=instance1
Server Instance 2 :
----------------------------
standalone.bat -server-config=standalone-ha.xml -Djboss.socket.binding.port-offset=200 -Djboss.node.name=instance2 -Djboss.server.base.dir=instance2
Client Configuration :
------------------------------
remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false
remote.connections=default
remote.connection.default.host=localhost
remote.connection.default.port=4447
remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false
remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOPLAINTEXT=false
remote.clusters=ejb
# Connection configuration(s) for the "ejb" cluster (these are just random examples. You might have to add username and password
# or callbackhandler depending on the security configuration(s) of these cluster node servers.
remote.cluster.ejb.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false
remote.cluster.ejb.connect.options.org.xnio.Options.SSL_ENABLED=false