On 07/08/2014 10:11 AM, Duong Quynh (FSU1.Z8.IP) wrote:
Here you go, it's waiting in Sender.close() as seen from the stack.
Ah, your example code must be a little different from what you sent at
the beginning of the thread, as that did not call sender.close(). I was
assuming it was blocked in session.close() as per the example.
On the face of it this looks like perhaps a proton bug. There should
have been a detach emitted, but that seems not to be the case. I wonder
if perhaps the session window is somehow preventing that.
Could you try this new patch and see if that has any effect?
diff -up ./src/qpid/messaging/amqp/ConnectionContext.cpp.orig ./src/qpid/messaging/amqp/ConnectionContext.cpp
--- ./src/qpid/messaging/amqp/ConnectionContext.cpp.orig 2014-07-08 10:43:01.396355339 +0100
+++ ./src/qpid/messaging/amqp/ConnectionContext.cpp 2014-07-08 10:43:28.566356812 +0100
@@ -321,6 +321,7 @@ void ConnectionContext::detach(boost::sh
wakeupDriver();
while (pn_link_state(lnk->sender) & PN_REMOTE_ACTIVE) {
wait(ssn);
+ wakeupDriver();
}
ssn->removeSender(lnk->getName());
}
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
