See the following issue for details of the reason: https://issues.apache.org/activemq/browse/AMQ-2094
On 27 June 2010 04:01, RichardWang <riw...@gmail.com> wrote: > > Hi, > > I use ActiveMQ 5.2.0. I was trying to upgrade it to 5.3.2 but had issues > when 5.3.2 was running on Linux. The ActiveMQ clients, including producers > and consumers, were unable to connect to the ActiveMQ server. Strangely, > this issue only existed on Linux, not on Windows. When I ran ActiveMQ 5.3.2 > on Windows, all the clients were able to connect. > > After lots of digging, I found out it's the transportConnector setting that > was causing the problem. I had this setting in activemq.xml: > > <transportConnector name="openwire" uri="tcp://localhost:61616"/> > > After I changed it to this: > > <transportConnector name="openwire" uri="tcp://0.0.0.0:61616"/> > > The problem went away on Linux. > > Is this a known issue in 5.3.2? Can anyone shed some light on why this was > happening? > > Thanks, > Richard > > -- > View this message in context: > http://old.nabble.com/ActiveMQ-5.3.2-transportConnector-uri%3D%22tcp%3A--0.0.0.0%3A61616%22-tp29003712p29003712.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
