[
https://issues.apache.org/jira/browse/QPID-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-6392:
---------------------------------
Attachment: QPID-6392-reproducer.tar.gz
Attaching a reproducer. It creates a tx and auto ack session, opens/creates the
subscription and sends two messages, recieves one message, closes the tx
session (implicitly detaching the producer and subscriber), reopens the
subscriber on the auto-ack session, receives the other message, then tries to
detach the second subscriber object explicitly but doesnt get a detach response.
Steps to use:
1. Check out the new client source from:
https://git-wip-us.apache.org/repos/asf/qpid-jms.git or
https://github.com/apache/qpid-jms
2. Extract the attachment somewhere.
3. Run "mvn clean install -DskipTests" in the client checkout.
4. Start the broker.
5 Created a topic exchange called "MY_TOPIC" using: qpid-config --durable add
exchange topic MY_TOPIC
6. Run "mvn verify" in the reproducer dir, notice it log out the messages, say
it is closing the subscriber, then exit after timing out because that didnt
complete.
There is also a protocol trace of the traffic between client and broker
included in the tar.
> [C++ Broker] [AMQP 1.0] the broker didnt respond to a link detach request
> -------------------------------------------------------------------------
>
> Key: QPID-6392
> URL: https://issues.apache.org/jira/browse/QPID-6392
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.31
> Reporter: Robbie Gemmell
> Attachments: QPID-6392-reproducer.tar.gz
>
>
> In running some tests, I noticed a situation where the broker does not
> respond to a detach request for a durable subscriber link.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
