2 Replies Latest reply on Apr 29, 2009 8:15 AM by garytully

    Can't connect to MQ server as of 5.3.0.1

    dave.stubbs

      I've been using multiple releases of Fuse MQ over the last year, but the latest release no longer appears to accept connections from anything other than local clients.

       

      I've got both 5.2.0.2 and 5.3.0.1 on the same machine and I have no problems on the former, but copy across the config file and fire up the new version and the clients can't connect. I can't fins a reason why apart from when I shut down I get the following in the logs.

       

      2009-04-25 18:06:36,823 INFO  AdvisoryConsumer               - Failed to send remove command: javax.jms.JMSException: Transport disposed.

      javax.jms.JMSException: Transport disposed.

           at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:62)

           at org.apache.activemq.ActiveMQConnection.doAsyncSendPacket(ActiveMQConnection.java:1227)

           at org.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:1219)

           at org.apache.activemq.AdvisoryConsumer.dispose(AdvisoryConsumer.java:56)

           at org.apache.activemq.ActiveMQConnection.close(ActiveMQConnection.java:606)

           at org.springframework.jms.connection.ConnectionFactoryUtils.releaseConnection(ConnectionFactoryUtils.java:81)

           at org.springframework.jms.listener.AbstractJmsListeningContainer.refreshSharedConnection(AbstractJmsListeningContainer.java:385)

           at org.springframework.jms.listener.DefaultMessageListenerContainer.refreshConnectionUntilSuccessful(DefaultMessageListenerContainer.java:779)

           at org.springframework.jms.listener.DefaultMessageListenerContainer.recoverAfterListenerSetupFailure(DefaultMessageListenerContainer.java:761)

           at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:892)

           at java.lang.Thread.run(Thread.java:619)

      Caused by: org.apache.activemq.transport.TransportDisposedIOException: Transport disposed.

           at org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:74)

           at org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:40)

           at org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)

           at org.apache.activemq.ActiveMQConnection.doAsyncSendPacket(ActiveMQConnection.java:1225)

           ... 9 more

      2009-04-25 18:06:36,848 INFO  BrokerService                  - ActiveMQ JMS Message Broker (localhost, ID:atlas-65290-1240678116192-0:0) stopped

       

      This is running on a Windows server by the way, JDK 6.0.6

       

      I've tried telnetting to the openwire port which I can do just fine from localhost, but from my remote system the socket does not open. I thought it was a firewall issues at first until I tried on the older release which works perfectly.

       

      I'd love to know what's going on this time.

        • 1. Re: Can't connect to MQ server as of 5.3.0.1
          chimanlei

          I encountered the same issue. What I did to fix this issue to change the transportConnector uri not to use "localhost". Instead, using "0.0.0.0" to allow remote connections. see the example config below. It works for me and hope it works for you.

           

           

          • 2. Re: Can't connect to MQ server as of 5.3.0.1
            garytully

            Use of an ip address or hostname or the widlcard address of 0.0.0.0 is the correct fix here. There is a change of behavior in that regard. See the section : "Change of behavior for multihomed hosts using "tcp://localhost" in the  5.3.0.1 release note .

            Windows treats the loopback address and regular internet address as separate network interfaces so it is multihomed by default. localhost typically means the loopback interface.