[AMQ-6368] Non-blocking redelivery does not calculate exponential delivery properly

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 5.13.3
• Component/s: JMS client
• Patch Info: Patch Available
• Assignee: Unassigned
• Reporter: Szymon Jachim
• Created: 20/Jul/16 09:58
• Updated: 21/Aug/18 08:28

Description

Non-blocking redelivery does not calculate exponential delivery properly when retries of delivery are interspersed with (successful) deliveries of other mes sages.

This is caused by the fact that last redelivery delay is stored in a field and is overwritten delivery of other messages. A possible fix is that redelivery delay can be calculated each time by simply doing multiplications in a loop (as it is done in broker) or using mathematical exponent function. At the same time redelivery count can not be a single field but an array with a counter per each message waiting for client side non-blocking redelivery.

I can provide a patch for this and a unit tests.

Issue Links

• duplicates: AMQ-5730 When nonBlockingRedelivery is set to true, redelivery delays can be incorrect
• is related to: AMQ-3597 Enable RedeliveryPolicy to determine next delay independent of the consumer
• is related to: AMQ-1853 Optional non-blocking redelivery