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 09:26:05 GMT
Hi,

I guess that you use failover: URI on the client connection factory ?

Anyway, the client "knows" that the master failed. But the failover:* 
URI should do the trick.

Regards
JB

On 11/01/2013 09:31 AM, danaR wrote:
> I have a question about the default behavior of ActiveMQ 5.8.0 in a
> master/slave configuration (JDBC master/slave).
>
> We have a simple test of sending/receiving persistent messages, with
> acknowledgement mode AUTO_ACKNOWLEDGE.
>
> During the test we force a failover (we stop the current broker, so the
> slave will become master).
>
> The problem (at least for us it's a problem) is that when the client fails
> over to the new master broker, it receives duplicate messages.
> In the logs, we get this warning  "Ignoring ack received before dispatch;
> result of failover with an outstanding ack. Acked messages will be replayed
> if present on this broker."
>
> So I'm guessing that this is the normal behavior and the client should be
> the one that filters out the duplicates?
>
> Can anyone confirm that this is the expected behavior?
> And also, is there a configuration that could prevent this from happening?
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Master-Slave-failover-behaviour-tp4673622.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