activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré ...@nanthrax.net>
Subject Re: Master/Slave failover behaviour
Date Fri, 01 Nov 2013 11:35:42 GMT
Yes, failover, should "wait" to reconnect to the promoted master.

You have only master/slave (no network of brokers), right ?

Regards
JB

On 11/01/2013 10:48 AM, danaR wrote:
> Hi,
> Thank you for the reply.
> Yes, we are using a URI like this:
> failover:(tcp://192.168.0.195:61616,tcp://192.168.0.196:61616)?initialReconnectDelay=100&trackMessages=true
>
> Still, I didn't understand your answer.
> Should using failover have taken care of our problem (the duplicate messages
> that we receive)?
> Or is it normal that the client receives duplicates when it fails over to
> the other broker (given the warning that we saw in the logs) ?
>
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Master-Slave-failover-behaviour-tp4673622p4673626.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Mime
View raw message