[AMQ-5730] When nonBlockingRedelivery is set to true, redelivery delays can be incorrect

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 5.15.3
• Component/s: Broker
• Assignee: Jean-Baptiste Onofré
• Reporter: arnaud hoareau
• Created: 15/Apr/15 14:54
• Updated: 23/Aug/18 17:19

Description

If nonBlockingRedivery is set to true and several message transactional deliveries are rollbacked by the same message consumer, their redelivery delay will interfer with each other.

Ex:
1) A first message delivery is rollbacked.

2) A second message is consumed by the same message consumer and delivery of second message is also rollbacked.

3) First message is redelivered after initial delay and is rollbacked.

4) Second message is delivered after initial delay and is rollbacked.

5) First message is redelivered after delay according to values of parameters useExponentialBackOff, backOffMultiplier, maximumRedeliveryDelay and useCollisionAvoidance.

6) Second message is redelivered after delay according to values of parameters but also according the value of the delay consumer of the previous message, stored in message consumer. For example, if last first message redelivery delay was x (computed at step 5), the current delay of step 6 will be at backoffmultiplier * x (if used).

7) Again, next first message redelivery delay will be impacted by last second message redelivery delay, etc.

A message redelivery should not impacted by other messages redelivery delay and should only be computed by the number of redeliveries.

Issue Links

• is duplicated by: AMQ-6368 Non-blocking redelivery does not calculate exponential delivery properly