Actually the behaviour is the same. Just specify all the servers in the client properties file. If will try to connect to a live one if the other specified are dead/down.

For instance I have in jboss-ejb-client.properties:

remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false

 

remote.connections=perf18,perf19,perf20,perf21

 

remote.connection.perf18.host=perf18

remote.connection.perf18.port=4447

remote.connection.perf18.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false

remote.connection.perf18.channel.options.org.jboss.remoting3.RemotingOptions.MAX_OUTBOUND_MESSAGES=100000

 

remote.connection.perf19.host=perf19

remote.connection.perf19.port=4447

remote.connection.perf19.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false

remote.connection.perf19.channel.options.org.jboss.remoting3.RemotingOptions.MAX_OUTBOUND_MESSAGES=100000

 

remote.connection.perf20.host=perf20

remote.connection.perf20.port=4447

remote.connection.perf20.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false

remote.connection.perf20.channel.options.org.jboss.remoting3.RemotingOptions.MAX_OUTBOUND_MESSAGES=100000

 

remote.connection.perf21.host=perf21

remote.connection.perf21.port=4447

remote.connection.perf21.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false

remote.connection.perf21.channel.options.org.jboss.remoting3.RemotingOptions.MAX_OUTBOUND_MESSAGES=100000

and 2 of shich hosts are not even deployed yet. After you connect to one you will get a current cluster view.

Rado