[AMQ-5513] redelivery count incremented in error for unconsumed prefetched messages

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.10.0
• Fix Version/s: 5.11.0
• Component/s: Broker, JMS client
• Labels: DLQ redelivery
• Assignee: Gary Tully
• Reporter: Gary Tully
• Created: 09/Jan/15 13:18
• Updated: 21/Apr/15 15:06
• Resolved: 09/Jan/15 13:33

Description

If a consumer with prefetch>0 does an immediate close, without consuming any messages. Spring DMLC with small timeout or receiveNoWait for example. The broker will have dispatched and will want to redispatch to another consumer and will have incremented the redelivery count in error.
After 6 (default redelivery attempts) a consumer will poison ack and the message will go to the DLQ.

A simple consumer create/close then create/receive with pending messages will demo this.
true for queue consumers and durable topic subs

Issue Links

• is related to: AMQ-1730 Bad use of Jms field JMSXDeliveryCount. Related to RedeliveryCount and message prefetch
• is related to: AMQCPP-558 Port fix for AMQ-5513
• is related to: AMQNET-497 Port fix for AMQ-5513
• relates to: AMQ-5735 increment redeliverCounter in the absence of client supplied information