Is the AMQ message broker running on the server machine and listening on port 61616?
If so, try telnet'ing to xxx.yyy.zzz.xyz 61616 and see if the broker responds. Joe ActiveMQ Ref Guide - http://bit.ly/AMQRefGuide test4john wrote: > > 1. brand new installation of tomcat 6; > > 2. activemq-all-5.3.2.jar put under lib; > > 3. activemq-web-console-5.3.2.war put under webapps; > > 4. start tomcat and > http://localhost:8080/activemq-web-console-5.3.2/queues.jsp works fine; > > 5. connectionFactory = new > ActiveMQConnectionFactory(ActiveMQConnection.DEFAULT_USER, > ActiveMQConnection.DEFAULT_PASSWORD, "tcp://localhost:61616"); > mainQueueConnection = > connectionFactory.createConnection(); > mainQueueConnection.start(); > works fine; > > 6. if run the same code from another machine, only change "localhost" to > the ip of the server machine(xxx.yyy.zzz.xyz), exception caught: > javax.jms.JMSException: Could not connect to broker URL: > tcp://xxx.yyy.zzz.xyz:61616. Reason: java.net.ConnectException: Connection > refused: connect > > 7. even on the same machine (the server machine), if change "localhost" to > ip, exception happened: > javax.jms.JMSException: Could not connect to broker URL: > tcp://xxx.yyy.zzz.xyz:61616. Reason: java.net.ConnectException: Connection > timed out: connect > > any idea? > > thanks! > > -- View this message in context: http://old.nabble.com/Connection-refused-with-embeded-AMQ-in-Tomcat-tp28700068p28700780.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
