You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Gary Tully <ga...@gmail.com> on 2011/11/01 12:15:20 UTC

Re: Does tracking messages may cause reduplicate messages?

in the case of failover with a pending send, so a message send where
the reply from the broker is lost, the state tracker with tracking
enabled, will resend the message on a reconnect.
If the message is already in the store, the producerAudit persisted by
the store will detect the duplicate send and ignore it.
so, yes it is. See the
org.apache.activemq.transport.failover.FailoverTransactionTest for a
unit test that simulates this.

2011/10/31 SuoNayi <su...@163.com>:
> Hi all, is it possible to cause the client to send reduplicate messages to broker when enable tracking messages?



-- 
http://fusesource.com
http://blog.garytully.com

Reply:Re: Does tracking messages may cause reduplicate messages?

Posted by SuoNayi <su...@163.com>.
Thanks Gary,what if producer failover to the other broker which is networked with the previous broker?
In this case, the other broker which does not know the message sent by the producer before its failover.
So the reduplicate messages are coming out,arenot they?




At 2011-11-01 19:15:20,"Gary Tully" <ga...@gmail.com> wrote:
>in the case of failover with a pending send, so a message send where
>the reply from the broker is lost, the state tracker with tracking
>enabled, will resend the message on a reconnect.
>If the message is already in the store, the producerAudit persisted by
>the store will detect the duplicate send and ignore it.
>so, yes it is. See the
>org.apache.activemq.transport.failover.FailoverTransactionTest for a
>unit test that simulates this.
>
>2011/10/31 SuoNayi <su...@163.com>:
>> Hi all, is it possible to cause the client to send reduplicate messages to broker when enable tracking messages?
>
>
>
>-- 
>http://fusesource.com
>http://blog.garytully.com