activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j0llyr0g3r <timo.roess...@wincor-nixdorf.com>
Subject Re: Simple networkConnector question
Date Mon, 20 Aug 2007 19:27:02 GMT

Hey, 

thx for the hint.

Funny, i always used it like that, but i always thought this would be some
kind of dirty hack and there would be a "clean" way to set up broker
connections.......:-)



ttmdev wrote:
> 
> transportConnector elements are used by brokers to listen for and accept
> connection requests from clients  and other brokers.
> 
> Joe
> 
> 
> 
> j0llyr0g3r wrote:
>> 
>> Hi folks, 
>> 
>> i got a really simple question and i hope someone can help me out. 
>> 
>> I simply don't get it: I just want to connect two brokers, let's call
>> them A and B.
>> 
>> Ok, so my broker A looks like this:
>> 
>>    <transportConnectors>
>>          <transportConnector  name="openwire" uri="tcp://localhost:61610"
>> discoveryUri="multicast://default"/>
>>       </transportConnectors>
>>  
>>       <networkConnectors>
>>         <networkConnector name="B" uri="static:(tcp://localhost:61818)"
>> />
>>       </networkConnectors>
>> 
>> Simple thing. Listen on 61610 for consumers and producers and make a
>> connection to another broker on 61818.
>> 
>> But HOW do i tell Broker B to listen on port 61818 for other broker
>> connections?
>> 
>> The transportConnectors are only for consumers / producers, right? So how
>> do tell broker B to listen on port 61818?
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Simple-networkConnector-question-tf4300784s2354.html#a12242314
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message