[AMQ-5146] RedeliveryPolicy exceeded for crashing consumer

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.9.1
• Fix Version/s: 5.10.0
• Component/s: JMS client
• Labels: DLQ redelivery redeliveryPolicy transaction
• Assignee: Gary Tully
• Reporter: Gary Tully
• Created: 15/Apr/14 12:21
• Updated: 24/Nov/16 16:41
• Resolved: 16/Apr/14 14:57

Description

A consumer with a transacted session that dies after receive or in onMessage (due to some of the message content for example), but before the a transaction can complete will continue to receive the message.
The connection will die, the transaction will rollback, the broker will increment the redeliveryCounter and redispatch the message.
However the redeliveryPolicy, which is only checked on rollback (client side) will never kick in.
the result is infinite redelivery with an ever incrementing redeliveryCounter.
It is a reasonable expectation that this message would eventually find its way into the dlq.
The broker redelivery plugin does not help because it is triggered by the client side poison ack.

Either the broker redelivery plugin can get involved before dispatch, or a client can do a predispatch check.

Issue Links

• breaks: AMQ-5156 Multiple tests using durable subs are failing
• is related to: AMQCPP-552 Honor RedeliveryPolicy for message redelivered by the Broker.
• is related to: AMQNET-489 Port fixes from AMQ-5146 to NMS.ActiveMQ
• relates to: AMQ-6517 Make redelivery policy preDispatch check optional