Chuck Rolke created AMQ-5433:
--------------------------------
Summary: AMQP messages stuck in broker when receiver detaches
while receiving
Key: AMQ-5433
URL: https://issues.apache.org/jira/browse/AMQ-5433
Project: ActiveMQ
Issue Type: Bug
Components: AMQP
Affects Versions: 5.11.0
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
Reporter: Chuck Rolke
[Amqp.Net Lite|https://amqpnetlite.codeplex.com/] 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|https://amqpnetlite.codeplex.com/SourceControl/latest#test/Test.Amqp.NetMF/LinkTests.cs].
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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)