Hi there,
I'd like to setup multiple initial connections (EJB receivers) for a remote standalone client to a clustered server. I expected to achieve this easily with the following configuration in jboss-ejb-client.properties:
remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false
remote.connections=default,other
remote.connection.default.host=192.168.0.1
remote.connection.default.port=4447
remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false
remote.connection.other.host=192.168.0.2
remote.connection.other.port=4447
remote.connection.other.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false
This works fine for a non-clustered multiple-server setup but not if the servers are clustered like this:
./standalone.sh -c standalone-ha.xml -Djboss.node.name=Server1 -b=192.168.0.1 -bmanagement=192.168.0.1
./standalone.sh -c standalone-ha.xml -Djboss.node.name=Server2 -b=192.168.0.2 -bmanagement=192.168.0.2
The application hangs while attempting to lookup an EJB.
The log up to this point is as follows:
15.08.2012 20:45:15 org.jboss.ejb.client.EJBClient <clinit>
INFO: JBoss EJB Client version 1.0.10.Final
15.08.2012 20:45:17 org.xnio.Xnio <clinit>
INFO: XNIO Version 3.0.3.GA
15.08.2012 20:45:17 org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.0.3.GA
15.08.2012 20:45:17 org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 3.2.7.GA
15.08.2012 20:45:18 org.jboss.ejb.client.remoting.VersionReceiver handleMessage
INFO: EJBCLIENT000017: Received server version 1 and marshalling strategies [river]
15.08.2012 20:45:18 org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver associate
INFO: EJBCLIENT000013: Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@4824de7d, receiver=Remoting connection EJB receiver [connection=Remoting connection <31f9338f>,channel=jboss.ejb,nodename=Server1]} on channel Channel ID c98a47cb (outbound) of Remoting connection 348dcd5d to /192.168.0.1:4447
I get the same behaviour with both the latest nightly AS 7 build as well as the current EAP 6.
Any idea what could be wrong with my configuration - or is this a bug?