Hi,

Yes, there's a mode to support routing messages from one broker to another (store and forward). There's however a major limitation to it:

"Note though that a store and forward network is not a solution for message HA; if a broker fails in a Store and Forward network, the messages owned by that broker remain inside the broker's persistent store until the broker comes back online. If you need HA of messages then you need to use Master/Slave described above."

http://activemq.apache.org/how-do-distributed-queues-work.html

  - Micke

----- Original Message -----
From: "John Mazzitelli" <mazz@redhat.com>
To: "Discussions around Hawkular development" <hawkular-dev@lists.jboss.org>
Sent: Thursday, May 14, 2015 4:27:25 PM
Subject: Re: [Hawkular-dev] The components, glue and kettle

Its been a while since I looked at the different distributed models for ActiveMQ but I thought there was more configurations available than simply master/slave.

I thought you could cluster brokers such that messages sent to one broker, could be received to consumers connected to other brokers and vice versa, with message persistence providing fault tolerance.

IIRC, I do remember in my testing I ran two kettle instances and sending messages via curl to one server was able to distribute those messages to consumers on the other.

As I understand it, isn't master/slave more for failover (that is, if the master goes down, the slave takes over)?

Again, its been a while since I looked into it, but I have to believe as mature as ActiveMQ is, that there are configurations of it we can use for distributed messaging in a way we need. I'm specifically talking about the later versions (like 5.10 we are using currently).

----- Original Message -----