Hi Tim,
Thank you for your extensive reply. If I can get it to work by
hardcoding the mcNetworkInterface value first, I'm more than willing to
spend some additional time into getting a nicer permanent solution and
contributing this back to the ActiveMQ project.
However, I still don't have mu
Leave the transportConnector's uri property alone as the original value of
tcp://0.0.0.0:61618; that's the IP for brokers to use when talking to each
other, but doesn't play when they're finding out about one another.
The way this is supposed to work (follow along at
https://github.com/apache/acti
Hi all,
I tried with the latest ActiveMQ 5.15.1 as well, but I unfortunately get the
same result: it still won't do the automatic clustering, while locally using
VMs this still works.
Thanks,
Jeroen...
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hi all,
I’m stuck with getting an ActiveMQ cluster going within a Docker
environment using Weave. The environment runs on an Amazon AWS ECS
Cluster of 2 EC2 Instances running in the same Region, but in different
Availability Zones. The clustering of ActiveMQ must rely on multicast
due to the
