redelivery is managed client side, the broker typically just fires out the
message to a consumer and it is either acked or not. If there is a restart
and the message was not acked it will be redelivered. There is an option to
have kahadb rewrite the message to persist the delivery count
https://is
hi,
version: activemq-5.8.0
we don't want client/consumer redelivery, so therefore we have set
maximumRedeliveries=0 on the connectionFactory
(ActiveMQConnectionFactory.java). Simple local (single-instance-broker)
tests verfied that no redelivery was performed.
today we tried a simple failover s
