Fixed by commits up to & including r944261
There is no information on bad and expected behavior and/or symptoms. It is impossible to work on this BZ at the moment. Could you possibly add the description, please? Raising NEEDINFO.
To test, create a client that has one thread doing a fetch (with an infinite timeout), and has the other attempting to close the session after a short time. The second thread will be locked out by the first thread prior to this fix. You could also replace the attempted close with an attempt to send on the second thread; again the infinite wait on fetch on the first thread will lock the sender out.
Frantisek, is this still something you want to test?
The issue has been fixed, tested on RHEL 5.7 / 6.1 i[36]86 / x86_64 on packages: python-qpid-0.10-1.el5.noarch python-qpid-qmf-0.10-10.el5.i386 qpid-cpp-client-0.10-8.el5.i386 qpid-cpp-client-devel-0.10-8.el5.i386 qpid-cpp-client-devel-docs-0.10-8.el5.i386 qpid-cpp-client-ssl-0.10-8.el5.i386 qpid-cpp-server-0.10-8.el5.i386 qpid-cpp-server-cluster-0.10-8.el5.i386 qpid-cpp-server-devel-0.10-8.el5.i386 qpid-cpp-server-ssl-0.10-8.el5.i386 qpid-cpp-server-store-0.10-8.el5.i386 qpid-cpp-server-xml-0.10-8.el5.i386 qpid-java-client-0.10-6.el5.noarch qpid-java-common-0.10-6.el5.noarch qpid-java-example-0.10-6.el5.noarch qpid-qmf-0.10-10.el5.i386 qpid-qmf-devel-0.10-10.el5.i386 qpid-tools-0.10-6.el5.noarch rh-qpid-cpp-tests-0.10-8.el5.i386 -> VERIFIED