activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <>
Subject Re: Configuring two activemqs on docker as primary and secondary
Date Wed, 24 Oct 2018 12:59:45 GMT
If you're running Docker within a management framework such as DC/OS
(Mesos), that framework might provide a DNS service in which you can
register your Docker containers, which would let you use the same
hostname-style addressing scheme you used previously.

I believe you could also use the hostname of the host that's running
Docker, with the mapped port number that Docker maps to your ActiveMQ port,
if that mapping is known in advance.

A lot depends on how you're actually using Docker, which you haven't
described. And since these questions really have nothing to do with
ActiveMQ (the question is about how to address a process running in Docker
from outside of the Docker container), if the answers you're getting here
aren't enough, you should probably post your question to either
StackOverflow or a Docker-specific mailing list (I assume there's one of


On Tue, Oct 23, 2018, 11:25 PM Jean-Baptiste Onofré <> wrote:

> Hi,
> you can use a shared volume between the two docker containers if you use
> master/slave.
> In the case of a network of brokers, you can't use multicast, so use
> static instead with docker IP addresses.
> Regards
> JB
> On 24/10/2018 06:58, abhilash128 wrote:
> > Hi,
> >
> > Iam trying to run two activemqs on docker as one of two is primary and
> the
> > other is secondary. I need to link them both to communicate each other
> with
> > network connectors. Earlier i use to do it by giving Hostname on VMs.
> >
> > Could someone please help how to configure this using Docker
> >
> >
> >
> > --
> > Sent from:
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message