activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark White <m...@somsip.com>
Subject Failover and updateClusterClients
Date Wed, 23 Jun 2010 05:02:30 GMT

I'm a newbie at this, so please excuse any limitations in my understanding.

We're looking at a load-balanced network of brokers with failover, using a
fixed list of URIs with 4 servers (A - D). We'll be using a common config
across brokers (except broker name). A JWS client will be used.

Client:
failover:(nio://A:61616,nio://B:61616,nio://C:61616,nio://D:61616)

Brokers:
<networkConnector name="example"
uri="static://(nio://A:61616,nio://B:61616,nio://C:61616,nio://D:61616)"/>
...
<transportConnector name="openwire"
uri="failover:(nio://A:61616,nio://B:61616,nio://C:61616,nio://D:61616)"
updateClusterClients="true" />

Questions:

1) Does it matter if the broker's own IP is included in networkConnector?

2) If broker A goes down, and a client attempts to connect to broker A, is
it 'timeout' that affects how quickly the client will failover to a
different broker?

3) The broker cluster is aware that A has dropped. How is
updateClusterClients represented at the client? Would it be similar to the
client connecting using a random broker from
"failover:(nio://B:61616,nio://C:61616,nio://D:61616)"?

4) If broker A is restored, will the client be advised of this on the next
successful communication with any broker? If not, when or how?

Thanks for any clarification anyone can give.


Mark...
-- 
View this message in context: http://old.nabble.com/Failover-and-updateClusterClients-tp28967819p28967819.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message