My main question would be, do you really *need* to spread the load among
multiple brokers? If you've got exclusive consumers on a lot of different
queues then you're already drastically limiting performance since you're
eliminating concurrent message consumption from all those queues. Is a
single b
To: users@activemq.apache.org
Subject: Re: sequential requests in a cluster
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
n sending in several message groups, yet only
the master ends up processing all the groups.
thanks!
From: Matt Pavlovich
Sent: Friday, September 23, 2022 5:12 PM
To: users@activemq.apache.org
Subject: Re: sequential requests in a cluster
Hello Brock,
A ’slave’
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
