the case where it is necessary is when a client connection drops
between sending an ack and the broker receiving the ack. So the broker
will redispatch the message when the consumer reconnects (when
failover kicks in).
If there is no failover the consumer and connection will die.
If the ack is in a
Due to https://issues.apache.org/jira/browse/AMQ-5016 our large and stable
systems will hit the 2^31 + 1 message limit after a few days. I gather that the
"checkForDuplicates" flag will prevent the "Duplicate dispatch on connection"
issue. I can set that flag on just our highest volume queues bu
