[QPID-293] setting MessageListener after connection has started can cause messages to be "lost" on a internal delivery queue.

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: M1, M2
• Fix Version/s: M3
• Component/s: JMS AMQP 0-x
• Assignee: Aidan Skinner
• Reporter: Martin Ritchie
• Created: 15/Jan/07 11:33
• Updated: 14/Mar/17 20:02
• Resolved: 08/Jul/08 09:13

Description

The message delivery process:

Mina puts a message on _queue in AMQSession and the dispatcher thread take()s from here and dispatches to the _consumers. If the _consumer doesn't have a message listener set at connection start then messages are stored on _synchronousQueue (which needs to be > 1 to pass JMS TCK as multiple consumers on a session can run in any order and a synchronous put/poll will block the dispatcher).

When setting the message listener later the _synchronousQueue is just poll()'ed and the first message delivered the remaining messages will be left on the queue and lost, subsequent messages on the session will arrive first.