activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From michaelrobinson <c.michaelrobin...@gmail.com>
Subject 5.3 transportConnector now stricter - network of brokers
Date Tue, 27 Oct 2009 19:40:44 GMT

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-now-stricter---network-of-brokers-tp26083763p26083763.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message