activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Posta <christian.po...@gmail.com>
Subject Re: [Java ActiveMQ 5.8] How to get originate broker infomation
Date Mon, 28 Oct 2013 15:38:38 GMT
Also you could just deploy a camel route alongside your broker A and listen
to Broker B advisory messages and maintain the consumer list yourself.
Wouldn't be too difficult to do that.

On Monday, October 28, 2013, Christian Posta wrote:

> So that info is available as part of the network of brokers
> implementation, depending on how deep in the code you're trying to go or
> trying not to go. Take a look at DemandForwardingBridgeSupport it should
> have a list of bridged consumers... From there you can get the brokers
> they're bridged from. I'd have to check the code closer to see if there is
> a better way this is exposed through a more friendly API. Take a look when
> u get a sec and see if this is what you want.
>
> On Sunday, October 27, 2013, Gihan wrote:
>
>> Hi Ceposta,
>>
>> Thanks for the reply. Yes I have networked them together. I just only need
>> broker B name. Basically I want to maintain in each broker about
>> subscribers
>> that subscribes to this broker network. In broker A and B, if I subscribe
>> to
>> B's test topic then I want to maintain that info on broker A that there
>> is a
>> subscriber for broker B's test topic inside broker A like (Broker B - >
>> test
>> - > consumer Id).
>>
>> Is there are anyway to capture broker B information inside broker A, once
>> any consumer subscribes to broker B ?
>>
>> Thanks,
>> Gihan
>>
>>
>>
>> --
>> View this message in context:
>> http://activemq.2283324.n4.nabble.com/Java-ActiveMQ-5-8-How-to-get-originate-broker-infomation-tp4673265p4673268.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>
>
> --
> *Christian Posta*
> http://www.christianposta.com/blog
> twitter: @christianposta
>
>

-- 
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message