I think there's a handful of different ways to address this...
In general, it seems like your consumption isn't keeping up with your
production otherwise you wouldn't have such a large build-up of messages on
one of the brokers. It's a good idea to balance message production with
adequate consump
Thanks for the reply
I think we finally got our QDR configured in a pretty nice spot but it came
with a realization that I couldn’t have transactions and message selectors
available to consumers unless a connection was “pinned”(?) or passed
through(?) to the broker at a lower level which got rid o
Hi Dan, how far did you go with qpid dispatch?
http://qpid.2158936.n2.nabble.com/Dispatch-Router-questions-td7664965.html
To my mind, having an intermediary (qpid dispatch) route messages
from their source with end to end flow control, rather than doing
store and forward is the best approach. Or
we are using Artemis 2.8.1 and we have 2 nodes in a cluster (Jgroup, TCP
ping, load balancing=On Demand). we build each queue and address on each
node and put address settings and security settings on each node (via the
jolokia http api). the two nodes are behind a single vip so each incoming
conne
