Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <11563845.post@talk.nabble.com>
Date: Thu, 12 Jul 2007 09:36:42 -0700 (PDT)
From: hh_meta <helen_han@tvworks.com>
To: users@activemq.apache.org
Subject: Re: network of broker: message does not forward between brokers and
 to consumer
In-Reply-To: <4695A790.1090800@raytheon.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <11551902.post@talk.nabble.com> <4695A790.1090800@raytheon.com>


how to ensure NoB links are made? the logs from brokers do have something
about "waking up reconnect task", "adding new broker ...", does that mean
the network has been formed correctly?
Or, do I get an error when the broker is not added to the network?


Kit Plummer wrote:
> 
> I believe this has to do with the timing of the consumer connection and 
> the network creation.  You'll need to ensure that the consumer connects 
> after the NoB links are made.
> 
> hh_meta wrote:
>> broker A, broker B forms a network of brokers. remote consumer connects
>> to
>> the network using multicast discovery, it could connect to any of the
>> brokers in the network, let's say broker B. each broker has a producer.
>> when message sends out via broker B, it sends to consumer right away.
>> when
>> message sends out broker A, it does not forward to broker B as expected,
>> log
>> says "No subscriptions registered, will not dispatch message at this
>> time"
>> 
>> this does not happen alwasys though. broker network TTL set to 100,
>> dynamicOnly is false, conduitSubscription is false.
> 
> 

-- 
View this message in context: http://www.nabble.com/network-of-broker%3A-message-does-not-forward-between-brokers-and-to-consumer-tf4065507s2354.html#a11563845
Sent from the ActiveMQ - User mailing list archive at Nabble.com.