We have use case where message ordering should be preserved also in case of
rollback ie. other messages shouldn't be consumed until failed message
delivered succesfully. We have only one consumer on queue. However
documentation says:
"If a redelivery-delay is specified, Apache ActiveMQ Artemis
Documentation is kind of unclear about this:
"Make sure your consumers are distributed evenly across the different nodes
/if possible/. This is only an issue if you are creating and closing
consumers regularly. Since messages are always routed to the same queue once
pinned, removing a consumer
Is it default behavior if node loses it's consumers, messages with grouping
are not redelivered to another node even if redelivery is activated (also
message load balancing is ON_DEMAND)? We have no way to be sure that each
node queues has consumers at all times... :(
--
Sent from:
Found where those requests are coming from, so that problem is now
resolved... but the original one still remains ...
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
More trouble, when I make configuration changes (ansible task that runs on
each node serially, stops and starts artemis service), everything goes fine
but topology is left incomplete... when i checked logs every instances i
found this:
2018-06-21 14:20:21,765 ERROR
I tried to set 5 to cluster
connection, but it did'nt have any effect. Do I need to add also slave
connectors under static-connectors element?
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
We have static cluster with replication (master and slave instance / 1 host ,
3 hosts ) when I test shutting down 1 or more slaves topology is not
updated. Is this normal behavior, master notices that replicating fails and
stops that but thats it? When I try shutting down master instances
