googleactivemq

Connect to ActiveMQ from a different machine

For security reasons, the ActiveMQ ports in this solution cannot be accessed over a public IP address. To connect to ActiveMQ from a different machine, you must open ports 61616 and 8161 for remote access. Refer to the FAQ for more information on this.

IMPORTANT: Making this application’s network ports public is a significant security risk. You are strongly advised to only allow access to those ports from trusted networks. If, for development purposes, you need to access from outside of a trusted network, please do not allow access to those ports via a public IP address. Instead, use a secure channel such as a VPN or an SSH tunnel. Follow these instructions to remotely connect safely and reliably.

By default, all ActiveMQ transport connectors are enabled. To disable one of them, edit the /opt/bitnami/activemq/conf/activemq.xml file, and remove the line related to that connector:

<transportConnectors>
   <!-- DOS protection, limit concurrent connections to 1000 and frame size to 100MB -->
   <transportConnector name="openwire" uri="tcp://0.0.0.0:61616?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
   <transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
   <transportConnector name="stomp" uri="stomp://0.0.0.0:61613?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
   <transportConnector name="mqtt" uri="mqtt://0.0.0.0:1883?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
   <transportConnector name="ws" uri="ws://0.0.0.0:61614?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
</transportConnectors>

In case of changes to the configuration file, restart the server to have the changes take effect:

$ sudo /opt/bitnami/ctlscript.sh restart activemq

To test the server connectivity, run one of the ActiveMQ examples from a different machine using these instructions.

Last modification October 1, 2018