activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ttmdev <joe.fernan...@ttmsolutions.com>
Subject Re: NetworkTTL and Duplex Problem
Date Thu, 20 Dec 2007 16:29:07 GMT

Well, I pulled out my test environment for this and gave it a go against the
just-released AMQ 5.0 and things wouldn't work. This is my configuration.

[producer]-->[broker 1]<-->[broker 2]-->[broker 3]<--[consumer]

The messages would be forwarded from broker 1 to 2, but not 3. 

So, just for kicks I pulled out the duplex="true" on broker 1's cfg file to
get this.  

[producer]-->[broker 1]-->[broker 2]-->[broker 3]<--[consumer]

And it now works. It seems duplex=true is the fly-in-the-ointment. 

I have networkTTL=2 set for brokers 1 and 2. Broker 3 is just listening. 

Joe





tpounds wrote:
> 
> Is this configuration used on all 3 machines?
> 
> 
> ttmdev wrote:
>> 
>> Here's an example that works for me w/a similar 3 broker topology. 
>> 
>> <networkConnectors>  
>>      <networkConnector 
>>           name="twowaybridge" 
>>           uri="static:(tcp://remotehost:61616)"      			 
>>       	  networkTTL="2"
>>       	  duplex="true"/>
>> </networkConnectors> 
>> 
>> If you haven't done so already, try moving up to AMQ 5.0.
>> 
>> Joe
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/NetworkTTL-and-Duplex-Problem-tp14428941s2354p14439928.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message