activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cobrien <>
Subject Re: ActiveMQ 5.3.2 transportConnector uri="tcp://"
Date Tue, 29 Jun 2010 01:29:24 GMT

It appears that the java method getLocalHost on the java class , on which the transportConnector depends, can be 
ambiguous on linux. Its behavior is also dependent on the version of java
you are using. 

The issue and solutions discussed below:

ActiveMQ reference guide at


RichardWang 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://"/>
> 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:
Sent from the ActiveMQ - User mailing list archive at

View raw message