[QPID-3562] the 0-10 client path does not act as expected with asynchronous consumers using a prefetch of 1 on transacted sessions

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.12
• Fix Version/s: 0.13
• Component/s: JMS AMQP 0-x
• Assignee: Robbie Gemmell
• Reporter: Robbie Gemmell
• Created: 30/Oct/11 18:36
• Updated: 14/Mar/17 20:07
• Resolved: 30/Oct/11 18:49

Description

the 0-10 client path does not act as expected with asynchronous consumers using a prefetch of 1 on transacted sessions, as the client is able to hold a 2nd message during processing of a slow onMessage handler. This is because completions are sent to ensure credit does not dry up, allowing a large-than-prefetch number of messages to be consume in a given transaction. However, this is done prior to delivery to the client application, which causes the client to get sent a 2nd message by the broker.

This should isntead occur after delivery has completed (if it is necessary: the client may have committed, which sends accepting completions anyway) to give the expected behaviour.