Return-Path: 
 <dev-return-26171-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org>
Delivered-To: apmail-activemq-dev-archive@www.apache.org
Received: (qmail 36388 invoked from network); 6 Apr 2011 23:14:44 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 6 Apr 2011 23:14:44 -0000
Received: (qmail 19710 invoked by uid 500); 6 Apr 2011 23:14:44 -0000
Delivered-To: apmail-activemq-dev-archive@activemq.apache.org
Received: (qmail 19669 invoked by uid 500); 6 Apr 2011 23:14:44 -0000
Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@activemq.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@activemq.apache.org>
List-Post: <mailto:dev@activemq.apache.org>
List-Id: <dev.activemq.apache.org>
Reply-To: dev@activemq.apache.org
Delivered-To: mailing list dev@activemq.apache.org
Received: (qmail 19658 invoked by uid 99); 6 Apr 2011 23:14:43 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Apr 2011 23:14:43 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Apr 2011 23:14:42 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id E8E3995381
	for <dev@activemq.apache.org>; Wed,  6 Apr 2011 23:14:05 +0000 (UTC)
Date: Wed, 6 Apr 2011 23:14:05 +0000 (UTC)
From: "Arthur Naseef (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <844477992.39254.1302131645950.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (AMQ-3274) duplicate messages on Temporary Topics
 in network of brokers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394

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


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