You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by RichardWang <ri...@gmail.com> on 2010/06/27 05:01:24 UTC
ActiveMQ 5.3.2 transportConnector uri="tcp://0.0.0.0:61616"
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.
Re: ActiveMQ 5.3.2 transportConnector uri="tcp://0.0.0.0:61616"
Posted by cobrien <cl...@ttmsolutions.com>.
Richard,
As you pointed out this was an issue with previous releases and was
assumed fixed for 5.3.2 . Details can be found at
https://issues.apache.org/activemq/browse/AMQ-2094.
I will investigate this further. In the meantime I assume you are ok with
the fix that you found?
Clark
www.ttmsolutions.com
ActiveMQ reference guide at
http://bit.ly/AMQRefGuide
RichardWang wrote:
>
> Clark,
>
> I was able to ping 'localhost' on my Linux server. Since ActiveMQ 5.2.0
> worked fine with the uri="tcp://localhost:61616" setting on the same
> server, I suspect this is a ActiveMQ 5.3.2 issue.
>
> Thanks,
> Richard
>
>
> cobrien wrote:
>>
>> Richard,
>> What happens if you ping 'localhost'? If you don't get a response verify
>> that the line "127.0.0.1 localhost" is in your hosts file (etc/hosts).
>>
>>
>>
>> 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-tp29003712p29008657.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: ActiveMQ 5.3.2 transportConnector uri="tcp://0.0.0.0:61616"
Posted by RichardWang <ri...@gmail.com>.
Clark,
I was able to ping 'localhost' on my Linux server. Since ActiveMQ 5.2.0
worked fine with the uri="tcp://localhost:61616" setting on the same server,
I suspect this is a ActiveMQ 5.3.2 issue.
Thanks,
Richard
cobrien wrote:
>
> Richard,
> What happens if you ping 'localhost'? If you don't get a response verify
> that the line "127.0.0.1 localhost" is in your hosts file (etc/hosts).
>
>
>
> 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-tp29003712p29008094.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: ActiveMQ 5.3.2 transportConnector uri="tcp://0.0.0.0:61616"
Posted by cobrien <cl...@ttmsolutions.com>.
Richard,
What happens if you ping 'localhost'? If you don't get a response verify
that the line "127.0.0.1 localhost" is in your hosts file (etc/hosts).
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-tp29003712p29006534.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: ActiveMQ 5.3.2 transportConnector uri="tcp://0.0.0.0:61616"
Posted by Gary Tully <ga...@gmail.com>.
See the following issue for details of the reason:
https://issues.apache.org/activemq/browse/AMQ-2094
On 27 June 2010 04:01, RichardWang <ri...@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
Re: ActiveMQ 5.3.2 transportConnector uri="tcp://0.0.0.0:61616"
Posted by cobrien <cl...@ttmsolutions.com>.
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.