Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Fri, 1 Apr 2011 11:22:14 +0000 (UTC)
From: "Gary Tully (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <2036948238.27524.1301656934592.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (AMQ-2546) PubSubNoLocal not working correctly at
 network of brokers and durable topics
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Gary Tully updated AMQ-2546:
----------------------------

    Fix Version/s:     (was: 5.5.0)
                   5.6.0

> PubSubNoLocal not working correctly at network of brokers and durable topics
> ----------------------------------------------------------------------------
>
>                 Key: AMQ-2546
>                 URL: https://issues.apache.org/jira/browse/AMQ-2546
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.3.0
>         Environment: java 1.6.17
> spring 2.5.6
> Windows XP
>            Reporter: Antti Kallonen
>             Fix For: 5.6.0
>
>
> We have a store and forward network of brokers like this C1-B1------B2-C2. We don't want to receive our own messages from topic, and have set the pubSubNoLocal feature to true. When we first start the system, the feature is working correctly, and we are not receiving our own messages. But when shutdown the other broker and client, and restart them, the restarted client starts to receive it's own messages.

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