[
https://issues.apache.org/activemq/browse/AMQ-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-2030.
-----------------------------
Resolution: Fixed
resolved in 725323. WireFormat now at version 4.
> Topics Delivering Duplicate Messages when have cyclic network of brokers
> w/multicast discovery
> ----------------------------------------------------------------------------------------------
>
> Key: AMQ-2030
> URL: https://issues.apache.org/activemq/browse/AMQ-2030
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.2.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.3.0
>
>
> In a cyclic network using m/cast discovery. Every broker knows about ever
> other broker.
> Network of 3, broker1, broker2, broker2 - consumer on broker2, producer on
> broker1
> problem description:
> consumer on broker 2 is propagated to broker1 and broker3.
> Resulting bridged consumer on 1 is propagated to 2 and 3:
> - broker 2 ignores it because of the broker path match.
> - broker 3 bridges it and propagates the resulting consumer to 2 and 1. 2
> again ignores as does 1 because of broker path info..
> Resulting bridged consumer on 3 is now a duplicate of the subscription
> propagated to 3 via broker 1. This cannot be suppressed using broker path
> because 3 only sees the brokerpath to broker1.
> What is needed is a history of the original consumerId in the bridged
> subscripton such that subsequent subscriptions can be seen as duplicates.
> ConsumerInfo needs to contain a list of networkConsumerIds.
> To have this propagated needs a wireFormat version increment.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.