thank you for the reply, Matt!
interesting that you mentioned the sorting of the messages by queues, because
that is exactly what i am doing. sorry, i should have been more clear in my
initial post. each message sequence is grouped and then posted to its own
single queue, and no sequence spans
Hello Brock,
A ’slave’ broker in the technical sense does not have active transport
connectors, so clients are not able to process messages. The slave is used as a
standby instance during a failure scenario for the master broker.
Perhaps you have a different setup? Keep in mind— maintaining mes
I am running AMQ 5.15.x in a master/slave cluster setup with several queues.
while some queues have multiple consumers, others have only a single consumer
since their messages must be processed in the exact order they arrived. using
the "exclusive consumer" feature works fine with respect to mai
> I wouldn't mirror and send to the same broker!
That’s the problem I’m trying to solve.
I have disabled the core bridges on the mirror side, but that means there is an
extra step in failover – stop the bridge on the old active side, start on the
new active side. Dual mirroring was an easy sell
