Well this is a bug in the libraries, I've been looking at the code and here is (probably obvious for you :) ) problem:
1. Thread 1 acquires the FailoverMutex 2. Thread 2 acquires the MessageDeliveryLock 3. Thread 1 tries to acquire the MessageDeliveryLock 4. Thread 2 tries to acquire the FailoverMutex Thus the deadlock. Alex, I do not think that it has anything to do with closing Consumers from Listeners, it's just a side effect. Thank You, Eugene. -- View this message in context: http://apache-qpid-developers.2158895.n2.nabble.com/Deadlock-tp7581518p7581564.html Sent from the Apache Qpid developers mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
