You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by chahir <ch...@yahoo.fr> on 2007/06/12 16:33:44 UTC
duplicate messages when re-activate receiver
Hi,
I have 3 brokers which one has a sender application and the 2 others have
receiver applications.
I want to verify if messages will be successfully delivered if I disconnect
a receiver and activate the other many times.
The problem was that when I send messages (20000 for exple),the first
receiver will consume them until I disconnect him(the application and not
the broker).If I activate the other receiver, it will consume the rest.
At the end, when all the messages are sent, if I activate the first
receiver, it will consume messages already consumed by the 2nd from his
broker(duplicated messages).
Is there a solution to avoid messages duplication(Broker1 send their
messages to the 2nd and so the sender wil not send duplicated messages)?
Thank you for your answer.
Bye.
--
View this message in context: http://www.nabble.com/duplicate-messages-when-re-activate-receiver-tf3907725s2354.html#a11079399
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: duplicate messages when re-activate receiver
Posted by chahir <ch...@yahoo.fr>.
OK,
I'm using ActiveMQ 4.2-SNAPSHOT with persistent queues.
Hiram Chirino wrote:
>
> We would need more details like queue or topic, persistent or not,
> version being used. etc. etc.
>
> On 6/12/07, chahir <ch...@yahoo.fr> wrote:
>>
>> Hi,
>>
>> I have 3 brokers which one has a sender application and the 2 others have
>> receiver applications.
>> I want to verify if messages will be successfully delivered if I
>> disconnect
>> a receiver and activate the other many times.
>> The problem was that when I send messages (20000 for exple),the first
>> receiver will consume them until I disconnect him(the application and not
>> the broker).If I activate the other receiver, it will consume the rest.
>> At the end, when all the messages are sent, if I activate the first
>> receiver, it will consume messages already consumed by the 2nd from his
>> broker(duplicated messages).
>> Is there a solution to avoid messages duplication(Broker1 send their
>> messages to the 2nd and so the sender wil not send duplicated messages)?
>>
>> Thank you for your answer.
>>
>> Bye.
>> --
>> View this message in context:
>> http://www.nabble.com/duplicate-messages-when-re-activate-receiver-tf3907725s2354.html#a11079399
>> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com
>
>
--
View this message in context: http://www.nabble.com/duplicate-messages-when-re-activate-receiver-tf3907725s2354.html#a11115849
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: duplicate messages when re-activate receiver
Posted by Hiram Chirino <hi...@hiramchirino.com>.
We would need more details like queue or topic, persistent or not,
version being used. etc. etc.
On 6/12/07, chahir <ch...@yahoo.fr> wrote:
>
> Hi,
>
> I have 3 brokers which one has a sender application and the 2 others have
> receiver applications.
> I want to verify if messages will be successfully delivered if I disconnect
> a receiver and activate the other many times.
> The problem was that when I send messages (20000 for exple),the first
> receiver will consume them until I disconnect him(the application and not
> the broker).If I activate the other receiver, it will consume the rest.
> At the end, when all the messages are sent, if I activate the first
> receiver, it will consume messages already consumed by the 2nd from his
> broker(duplicated messages).
> Is there a solution to avoid messages duplication(Broker1 send their
> messages to the 2nd and so the sender wil not send duplicated messages)?
>
> Thank you for your answer.
>
> Bye.
> --
> View this message in context: http://www.nabble.com/duplicate-messages-when-re-activate-receiver-tf3907725s2354.html#a11079399
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>
>
--
Regards,
Hiram
Blog: http://hiramchirino.com