activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arthur Naseef (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-3274) duplicate messages on Temporary Topics in network of brokers
Date Wed, 06 Apr 2011 23:18:05 GMT

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

Arthur Naseef updated AMQ-3274:
-------------------------------

    Attachment: tempTopicDups.patch

Patch eliminating duplicates on temporary topics.  As the patch shows, subscriptions to temporary
destinations were being matched against the subscriptions in permanent regions, not the temp
regions.

> duplicate messages on Temporary Topics in network of brokers
> ------------------------------------------------------------
>
>                 Key: AMQ-3274
>                 URL: https://issues.apache.org/jira/browse/AMQ-3274
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.2
>            Reporter: Arthur Naseef
>            Priority: Critical
>         Attachments: tempTopicDups.patch
>
>
> Creating a network of brokers, duplicate messages are being seen on Temporary Topics.
> The network configuration used is as follows:
>         <networkConnectors>
>                 <networkConnector name="nw1_queues_from_nw2" uri="static:(tcp://127.0.0.1:60002)"
>                                   duplex="true" conduitSubscriptions="false" dynamicOnly="true"
>                                   networkTTL="7" suppressDuplicateQueueSubscriptions="true"
>                                   decreaseNetworkConsumerPriority="true"
>                                   bridgeTempDestinations="true"
>                                   >
>                         <excludedDestinations>
>                                 <topic physicalName=">" />
>                         </excludedDestinations>
>                 </networkConnector>
>                 <networkConnector name="nw1_topics_from_nw2" uri="static:(tcp://127.0.0.1:60002)"
>                                   duplex="true" conduitSubscriptions="true" dynamicOnly="true"
>                                   networkTTL="7" suppressDuplicateQueueSubscriptions="true"
>                                   decreaseNetworkConsumerPriority="true"
>                                   bridgeTempDestinations="true"
>                                   >
>                         <excludedDestinations>
>                                 <queue physicalName=">" />
>                         </excludedDestinations>
>                 </networkConnector>
>     </networkConnectors>
> Note there are 2 duplex connections between the brokers.  Changing to non-duplex connections,
the problem goes away with 2 brokers in the network, but reappears when a 3rd broker is added.
> The problem only affects temporary Topics; normal Topics work fine.
> A patch will be attached.  Also, a test case will be attached when it is available.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message