You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Eric (JIRA)" <ji...@apache.org> on 2010/07/27 11:39:52 UTC
[jira] Commented: (AMQ-2776) Connection refused when using
shortname in activemqurl
[ https://issues.apache.org/activemq/browse/AMQ-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60931#action_60931 ]
Eric commented on AMQ-2776:
---------------------------
In 5.3.2
With two distinct brokers on the same server with a single interface, and without localhost usage.
I experiment the same problem of connection refused on a multicast network connector connection. Only "0.0.0.0" seems to work as IP address of the transport connector
"name" of the current host, with or without domain extension, with useLocalHost=true or useLocalHost=false doesn't work.
It works in 5.3.0-5 fuse.
I don't know if using the virtual hostname associated to another interface in the /etc/hosts file, works. We must have this functionality in production environment to isolate flows for security reasons.
Eric-AWL
> Connection refused when using shortname in activemqurl
> ------------------------------------------------------
>
> Key: AMQ-2776
> URL: https://issues.apache.org/activemq/browse/AMQ-2776
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
> Affects Versions: 5.3.2, 5.4.0
> Environment: Suse 10 Sp2
> Reporter: vioa lu
> Fix For: 5.4.0
>
> Attachments: activemq-2776.patch
>
>
> 1. On server suse10sp268, start activemq , then run activemq-admin.bat browse --amqurl tcp://suse10sp268:61616 TEST.FOO , got excecption Caused by: javax.jms.JMSException: Could not connect to broker URL: tcp://suse10sp268:61616. Reason: java.net.ConnectException: Connection refused: connect
> at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35)
> at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:286)
> at org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:185)
> at org.apache.activemq.ra.ActiveMQConnectionSupport.makeConnection(ActiveMQConnectionSupport.java:79)
> at org.apache.activemq.ra.ActiveMQConnectionSupport.makeConnection(ActiveMQConnectionSupport.java:61)
> at org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedConnection(ActiveMQManagedConnectionFactory.java:169)
> ... 42 more
> Caused by: java.net.ConnectException: Connection refused: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
> at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
> at java.net.Socket.connect(Socket.java:519)
> at org.apache.activemq.transport.tcp.TcpTransport.connect(TcpTransport.java:483)
> at org.apache.activemq.transport.tcp.TcpTransport.doStart(TcpTransport.java:446)
> at org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:53)
> at org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:58)
> at org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:58)
> at org.apache.activemq.transport.WireFormatNegotiator.start(WireFormatNegotiator.java:72)
> at org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:58)
> at org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:58)
> at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:266)
> This happened also when got error starting activemq-ra module in geronimo
> https://issues.apache.org/jira/browse/GERONIMO-5371
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.