Thanks guys! I will try this out soon. -Trevor
rajdavies wrote: > > hi Joe this issue has been fixed recently: > https://issues.apache.org/activemq/browse/AMQ-1521 > > cheers, > > Rob > On Dec 20, 2007, at 4:29 PM, ttmdev wrote: > >> >> 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. >> > > > -- View this message in context: http://www.nabble.com/NetworkTTL-and-Duplex-Problem-tp14428941s2354p14443027.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
