This use-case requires message *redistribution* [1] which currently
requires using the ON_DEMAND message load-balancing policy as described in
the documentation. Since you're using STRICT you won't get message
redistribution.
Note, I sent a PR [2] over a year ago to support redistribution with bot
Hi,
1. ActiveMQ 5.15.14 will bring update Spring 4.3.x update addressing the CVE
(still maintained)
2. I’m still working on ActiveMQ 5.17.0 preparation (upgrading build with JDK
11, removing leveldb, upgrading to Spring 5).
So reasonably, ActiveMQ 5.17.0 won’t be on vote before Jan 21.
Regards
Hi all,
https://issues.apache.org/jira/browse/AMQ-8026
Interested to have an update on the above ticket. Does anyone have a
tentative release date for 5.17.0?
Sry to create a separate thread. Unable to continue on the below thread.
http://activemq.2283324.n4.nabble.com/Need-spring-upgrade-in-Acti
Hello,
We are running Artemis in a clustered setup with three nodes. We have a load
balancer in front of the nodes.
We want a durable subscriber to be unaware of which node it connects to. So if
the durable subscriber loose connection to instance nodeA, it can connect to
nodeB (which it hasn’t
