You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Antti Kallonen (JIRA)" <ji...@apache.org> on 2009/12/22 10:23:40 UTC

[jira] Created: (AMQ-2546) PubSubNoLocal not working correctly at network of brokers and durable topics

PubSubNoLocal not working correctly at network of brokers and durable topics
----------------------------------------------------------------------------

                 Key: AMQ-2546
                 URL: https://issues.apache.org/activemq/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


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.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (AMQ-2546) PubSubNoLocal not working correctly at network of brokers and durable topics

Posted by "SuoNayi Wang (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQ-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57125#action_57125 ] 

SuoNayi Wang commented on AMQ-2546:
-----------------------------------

You can see 
https://issues.apache.org/activemq/browse/AMQ-2561

> PubSubNoLocal not working correctly at network of brokers and durable topics
> ----------------------------------------------------------------------------
>
>                 Key: AMQ-2546
>                 URL: https://issues.apache.org/activemq/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
>
> 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.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (AMQ-2546) PubSubNoLocal not working correctly at network of brokers and durable topics

Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Snyder updated AMQ-2546:
------------------------------

    Fix Version/s: 5.5.0
                       (was: 5.4.1)

> PubSubNoLocal not working correctly at network of brokers and durable topics
> ----------------------------------------------------------------------------
>
>                 Key: AMQ-2546
>                 URL: https://issues.apache.org/activemq/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.5.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.
-
You can reply to this email to add a comment to the issue online.