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
 72.21.53.35 as permitted sender)
Message-ID: <9492074.post@talk.nabble.com>
Date: Thu, 15 Mar 2007 03:54:27 -0700 (PDT)
From: facboy <dnd1066@gmail.com>
To: users@activemq.apache.org
Subject: Re: [Spam: 5.0] daft question(s) about network of brokers
In-Reply-To: <BC0B32BB-1B11-4DD3-ABF1-674798D4F37C@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <9488895.post@talk.nabble.com>
 <ec6e67fd0703150150x47d19a99p3923862fe6e8c8d1@mail.gmail.com>
 <9491191.post@talk.nabble.com> <9491262.post@talk.nabble.com>
 <BC0B32BB-1B11-4DD3-ABF1-674798D4F37C@gmail.com>


yeah i've set something up so that it generates the broker name off the jboss
instance.

how does a durable topic subscription work with a network of brokers?  at
the moment if i have a durable topic subscriber on either broker, the other
one's 'Demand Forwarding Bridge' bombs out with the 'Durable Consumer'
connection exception.  is it possible to have this kind of configuration? 
or will it just not work?

thanks.


rajdavies wrote:
> 
> If the brokerName isn't set - it defaults to localhost - I would  
> strongly suggest you explicitly set the brokerName if you are using  
> more than one broker.
> 
> cheers.
> 
> 
> Rob Davies
> http://rajdavies.blogspot.com/
> 
> 
> 
> On 15 Mar 2007, at 09:52, facboy wrote:
> 
>>
>> hmm...i also started getting errors of this nature:
>>
>> 20:49:48,437 INFO  [DemandForwardingBridge] Network connection between
>> vm://jboss-2#8 and tcp://localhost/127.0.0.1:62626 shutdown due to  
>> a local
>> error:
>> javax.jms.JMSException: Durable consumer is in use for client:
>> NC_jboss-1_inboundjboss-2 and subscriptionName:  
>> jboss-2_topic.testTopic
>>
>> which i wasn't getting before.
>>
>>
>> facboy wrote:
>>>
>>> how do i embed the broker without specifying a broker name?  the  
>>> embedded
>>> broker always has a brokername = hostname, doesn't it?  if i use  
>>> 'vm://'
>>> then it doesn't seem to embed the broker properly, my MDBs don't  
>>> read the
>>> destinations any more.
>>>
>>> am i even configuring this correctly?  i want a 'network' of jboss
>>> instances so that I can send a message to a topic with a multicast  
>>> (or
>>> rendezvous) broker url, and an mdb on each jboss instance  
>>> listening to the
>>> topic will see the message.  does that make sense?
>>>
>>> it seemed to work correctly earlier today, but now it goes into some
>>> infinite loop of bouncing messages back and forth between the  
>>> brokers.
>>>
>>>
>>> James.Strachan wrote:
>>>>
>>>> On 3/15/07, facboy <dnd1066@gmail.com> wrote:
>>>>>
>>>>> I'm trying to setup a network of brokers here...currently running 2
>>>>> instances
>>>>> of jboss with ActiveMQ embedded.  both have virtually the same
>>>>> configuration
>>>>> (including the same brokerName).
>>>>
>>>>
>>>> Broker's names are intended to be unique. Its better to not specify
>>>> one if you're not gonna give them unique names (then it'll
>>>> auto-generate one).
>>>>
>>>>>  if i configure the brokers for multicast
>>>>> discovery and send a message to a topic on one of the brokers,  
>>>>> the other
>>>>> doesn't see it.  if i configure the brokers for rendezvous  
>>>>> discovery,
>>>>> then
>>>>> both can see the message on the topic.
>>>>>
>>>>> so,
>>>>> (1) is this because the multicast discovery agent is 'filtering  
>>>>> out'
>>>>> broadcasts that have the same broker name as itself, because it  
>>>>> thinks
>>>>> they
>>>>> are from itself?
>>>>
>>>> I think so yes
>>>>
>>>>> (2) is there a way around this, apart from manually changing all  
>>>>> the
>>>>> broker
>>>>> names to be different?
>>>>
>>>> Don't specify a broker name
>>>>
>>>>> (3) is there a downside to using rendezvous instead of multicast  
>>>>> (or
>>>>> vice
>>>>> versa)
>>>>
>>>> The only real downside is another jar dependency and not being  
>>>> able to
>>>> change the multicast address (so there's a chance of clashing with
>>>> other rendezvous stuff)
>>>>
>>>> -- 
>>>>
>>>> James
>>>> -------
>>>> http://radio.weblogs.com/0112098/
>>>>
>>>>
>>>
>>>
>>
>> -- 
>> View this message in context: http://www.nabble.com/daft-question% 
>> 28s%29-about-network-of-brokers-tf3406477s2354.html#a9491262
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/daft-question%28s%29-about-network-of-brokers-tf3406477s2354.html#a9492074
Sent from the ActiveMQ - User mailing list archive at Nabble.com.