activemq-users mailing list archives

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

Richard,
It appears that the java method getLocalHost on the java class
java.net.InetAddress , 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:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4665037
https://issues.apache.org/jira/browse/JCS-40


Clark 

www.ttmsolutions.com 
ActiveMQ reference guide at 
http://bit.ly/AMQRefGuide

 
 

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://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-tp29003712p29014161.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message