Awesome! Thanks man, you're a genius :D I'll try that out and let you know.
Btw, do you know what might be causing this - 2019-03-28 21:01:30,870 WARN [org.apache.activemq.artemis.core.server] AMQ222139: MessageFlowRecordImpl [nodeID=4b467f90-4f50-11e9-87df-fa163edb8703, connector=TransportConfiguration(name=master2-connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=10-31-100-103, queueName=$.artemis.internal.sf.my-cluster.4b467f90-4f50-11e9-87df-fa163edb8703, queue=QueueImpl[name=$.artemis.internal.sf.my-cluster.4b467f90-4f50-11e9-87df-fa163edb8703, postOffice=PostOfficeImpl [server=ActiveMQServerImpl::serverUUID=49dd2b82-4f50-11e9-a5f3-fa163ee44ef3], temp=false]@7d93e725, isClosed=false, reset=true]::Remote queue binding exampleQueue::jms.queue.exampleQueue4b467f90-4f50-11e9-87df-fa163edb8703 has already been bound in the post office. Most likely cause for this is you have a loop in your cluster due to cluster max-hops being too large or you have multiple cluster connections to the same nodes using overlapping addresses -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
