Hello Geoffry, On the machine with your broker, do you see the following in netstat?:
tcp 0 0 ::ffff:<server_ip>:61616 :::* LISTEN tcp 0 0 ::ffff:127.0.0.1:61616 :::* LISTEN If yes, from the consumer machine, can you now run: telnet <server_ip> 61616 and connect (to confirm the port is really accessible)? If yes, this is now an issue on your consumer. I am not understanding one thing though. How were you configuring your broker originally? I was expecting you to update an existing broker configuration file (whether it be outside OSGi, or defined inside OSGi as a spring-dm/blueprint file)...rather than creating a new one. regards, Gareth -- View this message in context: http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tp3334296p3337007.html Sent from the Karaf - User mailing list archive at Nabble.com.
