yea, that indicates that the listen should be on all network interfaces. Previously this was the behavior if "localhost" was used which was a security hole. For a discussion see: https://issues.apache.org/activemq/browse/AMQ-2094
2009/10/27 michaelrobinson <c.michaelrobin...@gmail.com> > > Not sure if this was intended or not but I could not find any relevant > issue > so I thought that I would post here in case anyone else runs into something > similar. We are currently in the process of attempting to upgrade from 5.2 > to 5.3 but ran into an issue with our "network of brokers". The > problem/exception was "Connection refused". With 5.2 our transportConnector > looked something like: > > ... > <transportConnectors> > <transportConnector name="openwire" uri="tcp://localhost:61616" > /> > </transportConnectors> > ... > > With this other brokers in the network could connect and store and forward > just fine but when we upgraded to 5.3 no brokers could connect > successfully. > Changing the above to: > > ... > <transportConnectors> > <transportConnector name="openwire" uri="tcp://0.0.0.0:61616" > /> > </transportConnectors> > ... > > resolves the issue. Is the above way the preferred way of assigning the > connector uri? > > Thanks, > > Michael > -- > View this message in context: > http://www.nabble.com/5.3-transportConnector-strictly---network-of-brokers-tp26083763p26083763.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
