[ 
https://issues.apache.org/jira/browse/ARTEMIS-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Bertram updated ARTEMIS-4312:
------------------------------------
    Description: Consider a set-up with two brokers clustered together and 
redistribution enabled and a address with about a dozen multicast subscription 
queues bound to it. If a consumer of one of those subscriptions goes offline, 
messages will begin to build up in the queue (as expected). When the consumer 
comes back online, whatever broker it attaches to first will have messages 
redistributed from the other broker in the cluster. When this redistribution 
happens the other multicast queues receive some of those redistributed messages 
(although not all of them) even though they had already received them 
previously.  (was: Consider a set-up with two brokers clustered together and 
redistribution enabled and a multicast address with about a dozen subscriptions 
bound to it. If a consumer of one of those subscriptions goes offline, messages 
will begin to build up in the queue (as expected). When the consumer comes back 
online, whatever broker it attaches to first will have messages redistributed 
from the other broker in the cluster. When this redistribution happens the 
other multicast queues receive some of those redistributed messages (although 
not all of them) even though they had already received them previously.)

> Duplicates with redistribution and multiple multicast queues on the same 
> address
> --------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-4312
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4312
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Justin Bertram
>            Assignee: Justin Bertram
>            Priority: Major
>
> Consider a set-up with two brokers clustered together and redistribution 
> enabled and a address with about a dozen multicast subscription queues bound 
> to it. If a consumer of one of those subscriptions goes offline, messages 
> will begin to build up in the queue (as expected). When the consumer comes 
> back online, whatever broker it attaches to first will have messages 
> redistributed from the other broker in the cluster. When this redistribution 
> happens the other multicast queues receive some of those redistributed 
> messages (although not all of them) even though they had already received 
> them previously.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to