Minor Description
Scenario on client:
- Employing RedeliveryPolicy with exponential backoff (keeping maximum redeliveries at default 6)
- Enabled non-blocking redelivery
- Receiving e.g. 100 consecutive poison messages which are rolled back repeatedly (which eventually should DLQ after max redeliveries)
This will result in massive redelivery delays due to a logic bug.
The reason is that redeliveryDelay is a field variable kept on the ActiveMQMessageConsumer, instead of being a property on the message - or that the redelivery delay was calculated per message based on the redelivery count.
When consecutive messages rollbacks multiple times, the redeliveryDelay field is continuously multiplied by the backoff multiplier, resulting in enormous delays.
Pull Request for fix, including test: https://github.com/apache/activemq/pull/843
