You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Arthur Naseef (Commented) (JIRA)" <ji...@apache.org> on 2012/01/31 23:55:58 UTC
[jira] [Commented] (AMQ-3274) duplicate messages on Temporary
Topics in network of brokers
[ https://issues.apache.org/jira/browse/AMQ-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13197353#comment-13197353 ]
Arthur Naseef commented on AMQ-3274:
------------------------------------
This is a relatively small change to fix the problem and I have provided a JUnit test case. Is there anything more I can do to help resolve it?
Note that I just checked the sources on the head (snapshot taken 01/12/2012), and the problem remains there.
> 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: AMQ3274Test.java, 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira