[AMQ-5433] AMQP messages stuck in broker when receiver detaches while receiving

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.11.0
• Fix Version/s: 5.12.0
• Component/s: AMQP

Environment

broker: snapshot apache-activemq-5.11-20141022.222801-124-bin.tar.gz
Wed Oct 22 22:28:02 UTC 2014
host: Linux Fedora 19 x64
client: Amqp.Net Lite self tests

• Assignee: Timothy A. Bish
• Reporter: Charles E. Rolke
• Created: 12/Nov/14 18:32
• Updated: 02/Apr/15 23:03
• Resolved: 02/Apr/15 23:03

Description

Amqp.Net Lite has a set of self tests that work OK when run against a Qpidd 0.30 (proton 0.8) broker. However, when run against ActiveMQ 5.10 or 5.11 SNAPSHOT one self tests causes a batch of messages to get stuck in the broker.
The self test in question is LinkTests.cs CloseBusyReceiver.

The test

• opens a sender and receiver to node q1.
• sends 20 messages.
• when the receiver receives the first message it closes the receiver and that causes an AMQP detach.
• then the test opens a second receiver and tries to drain the 20 messages.
  The test fails because the second receiver never receives anything. The AMQ web console shows the 20 messages in the queue.

Running the test again without clearing the queue results in 40 messages in the queue and the self test fails because the first receiver never receives any messages and thus never closes the busy receiver. The first 20 messages jam that queue.

Also, the messages are not received by tools that normally work fine, like qpid-receive.

This effect is 100% repeatable.

Protocol trace file to be attached