You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by Elber <sh...@hotmail.fr> on 2007/06/07 16:30:07 UTC
Routing information
Hello,
I've faced the pb of "NC_Broker_Outbound already exists" and I want to know
if there is a routing protocol which make brokers able to exchange
informations about connected clients.
So, a broker can have redundancy with clientId discovered and sent by a
neighbor.
Thank you.
--
View this message in context: http://www.nabble.com/Routing-information-tf3884166s2354.html#a11008998
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: Routing information
Posted by Elber <sh...@hotmail.fr>.
Thank you James.
James.Strachan wrote:
>
> On 6/7/07, Elber <sh...@hotmail.fr> wrote:
>>
>> Hello,
>>
>> I've faced the pb of "NC_Broker_Outbound already exists" and I want to
>> know
>> if there is a routing protocol which make brokers able to exchange
>> informations about connected clients.
>> So, a broker can have redundancy with clientId discovered and sent by a
>> neighbor.
>
> Networks of brokers kinda do that kinda thing for store & forward.
> Also Master/Slave for HA does similar things.
>
> Generally clientIDs are only required for durable topic subscriptions;
> which are a bit sucky at times - whereas Virtual Topics are way
> cooler...
>
> http://activemq.apache.org/virtual-destinations.html
>
>
> --
> James
> -------
> http://macstrac.blogspot.com/
>
>
--
View this message in context: http://www.nabble.com/Routing-information-tf3884166s2354.html#a11021693
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: Routing information
Posted by James Strachan <ja...@gmail.com>.
On 6/7/07, Elber <sh...@hotmail.fr> wrote:
>
> Hello,
>
> I've faced the pb of "NC_Broker_Outbound already exists" and I want to know
> if there is a routing protocol which make brokers able to exchange
> informations about connected clients.
> So, a broker can have redundancy with clientId discovered and sent by a
> neighbor.
Networks of brokers kinda do that kinda thing for store & forward.
Also Master/Slave for HA does similar things.
Generally clientIDs are only required for durable topic subscriptions;
which are a bit sucky at times - whereas Virtual Topics are way
cooler...
http://activemq.apache.org/virtual-destinations.html
--
James
-------
http://macstrac.blogspot.com/