Return-Path: 
 <dev-return-28018-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org>
X-Original-To: apmail-activemq-dev-archive@www.apache.org
Delivered-To: apmail-activemq-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 79F4F7724
	for <apmail-activemq-dev-archive@www.apache.org>;
 Thu, 11 Aug 2011 10:40:12 +0000 (UTC)
Received: (qmail 51329 invoked by uid 500); 11 Aug 2011 10:40:11 -0000
Delivered-To: apmail-activemq-dev-archive@activemq.apache.org
Received: (qmail 50436 invoked by uid 500); 11 Aug 2011 10:39:57 -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 49456 invoked by uid 99); 11 Aug 2011 10:39:51 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Aug 2011 10:39:51 +0000
X-ASF-Spam-Status: No, hits=-2000.8 required=5.0
	tests=ALL_TRUSTED,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; Thu, 11 Aug 2011 10:39:48 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 4293DB7C50
	for <dev@activemq.apache.org>; Thu, 11 Aug 2011 10:39:27 +0000 (UTC)
Date: Thu, 11 Aug 2011 10:39:27 +0000 (UTC)
From: "Michael Zamir (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <2081953311.27522.1313059167269.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1659273773.27492.1313058207243.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (AMQ-3446) Network of brokers does not pass
 messages when networkTTL is bigger then 1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


    [ https://issues.apache.org/jira/browse/AMQ-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083057#comment-13083057 ] 

Michael Zamir commented on AMQ-3446:
------------------------------------

Nice work Victor:)

In my words:
we have 3 brokers, A, B and C.
Each of them is connected to the other in a network connector

<broker name="A" >
     <networkConnector name="toBrokerB" uri="static:(tcp://brokerB:61618" networkTTL="*2*" />
     <networkConnector name="toBrokerC" uri="static:(tcp://brokerC:61618" networkTTL="*2*" />
</broker>

<broker name="B" >
     <networkConnector name="toBrokerA" uri="static:(tcp://brokerA:61618" networkTTL="*2*" />
     <networkConnector name="toBrokerC" uri="static:(tcp://brokerC:61618" networkTTL="*2*" />
</broker>

<broker name="C" >
     <networkConnector name="toBrokerA" uri="static:(tcp://brokerA:61618" networkTTL="*2*" />
     <networkConnector name="toBrokerB" uri="static:(tcp://brokerB:61618" networkTTL="*2*" />
</broker>



Client is registered on topic X into brokerA
*brokerA* then register on topic X to *broker B*
*brokerB* then register on topic X to *broker C*


Produce message to *brokerC* will work.
But then, if you stop *brokerB* and send/produce message to topic X on *brokerC*, the client consumer won't receive the message.




> Network of brokers does not pass messages when networkTTL is bigger then 1
> --------------------------------------------------------------------------
>
>                 Key: AMQ-3446
>                 URL: https://issues.apache.org/jira/browse/AMQ-3446
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.1, 5.4.2, 5.5.0
>            Reporter: VIctor Perepelitsky 
>              Labels: broker, network, networkBridge, networkConnector, ttl
>         Attachments: activemqTest.zip
>
>
> (Unit test is attached to prove the case)
> Given 3 brokers A, B and C.
> Each broker is connected to the others by a network bridge (so we have 3 brokers that are connected to each other)
> The networkTTL is 2 on all network connectors.
> Start broker A and B
> Subscribe consumer on A
> Start Broker C
> Stop Broker B
> Publish message to C
> Expected result:
> The consumer that is subscribed on A receives the message
> Actual result:
> Sometimes it works and sometimes the consumer does not receive the message.
> Additional info:
> From my understanding the problem appears since a broker subscribes as a consumer to other brokers only when there is a consumer that subscribed to this broker, but it does not try to renew subscription to other brokers when some (another) broker in its network fails (or stopped). 
> So we see the following situation:
> Client subscribed on topic X on A, A subscribed on topic X on B, B subscribed on topic X on C
> When we stop B, A does not subscribe on topic X on C and the message of topic X cannot pass from C to A.
> This BUG does not occur when networkTTL is 1 because subscription route in a network will be not be greater then 2

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