Description of problem: The receiver's fetch() method call is not finished after defined timeout. Note: behavior is as expected when using amqp0-10 protocol Version-Release number of selected component (if applicable): qpid-cpp-*-0.22-5 How reproducible: 100% Steps to Reproduce: 1. drain --timeout 1 --connection-options "{protocol:'amqp1.0'}" "amq.direct" 2. the program never ends Actual results: the timeout argument of receiver's fetch() method do not take effect Expected results: receiver's fetch() method call exits after defined timeout Additional info:
Fixed upstream by https://svn.apache.org/r1497749
Verified rhel 6.4 x86_64 / i686 x86_64 packages: perl-qpid-0.22-5.el6.x86_64 python-qpid-0.22-4.el6.noarch python-qpid-qmf-0.22-7.el6.x86_64 qpid-cpp-client-0.22-8.el6.x86_64 qpid-cpp-client-devel-0.22-8.el6.x86_64 qpid-cpp-client-devel-docs-0.22-8.el6.noarch qpid-cpp-client-rdma-0.22-8.el6.x86_64 qpid-cpp-client-ssl-0.22-8.el6.x86_64 qpid-cpp-debuginfo-0.22-8.el6.x86_64 qpid-cpp-server-0.22-8.el6.x86_64 qpid-cpp-server-devel-0.22-8.el6.x86_64 qpid-cpp-server-ha-0.22-8.el6.x86_64 qpid-cpp-server-rdma-0.22-8.el6.x86_64 qpid-cpp-server-ssl-0.22-8.el6.x86_64 qpid-cpp-server-store-0.22-8.el6.x86_64 qpid-cpp-server-xml-0.22-8.el6.x86_64 qpid-cpp-tar-0.22-8.el6.noarch qpid-java-client-0.22-5.el6.noarch qpid-java-common-0.22-5.el6.noarch qpid-java-example-0.22-5.el6.noarch qpid-proton-c-0.4-2.2.el6.x86_64 qpid-proton-c-devel-0.4-2.2.el6.x86_64 qpid-proton-debuginfo-0.4-2.2.el6.x86_64 qpid-qmf-0.22-7.el6.x86_64 qpid-qmf-debuginfo-0.22-7.el6.x86_64 qpid-qmf-devel-0.22-7.el6.x86_64 qpid-snmpd-1.0.0-12.el6.x86_64 qpid-snmpd-debuginfo-1.0.0-12.el6.x86_64 qpid-tests-0.22-4.el6.noarch qpid-tools-0.22-3.el6.noarch rh-qpid-cpp-tests-0.22-8.el6.x86_64 ruby-qpid-0.7.946106-2.el6.x86_64 i686 packages: qpid-qmf-debuginfo-0.22-7.el6.i686 qpid-cpp-client-rdma-0.22-8.el6.i686 qpid-cpp-server-xml-0.22-8.el6.i686 qpid-proton-c-devel-0.4-2.2.el6.i686 qpid-java-client-0.22-5.el6.noarch qpid-cpp-server-0.22-8.el6.i686 qpid-cpp-server-rdma-0.22-8.el6.i686 qpid-tools-0.22-3.el6.noarch qpid-java-example-0.22-5.el6.noarch qpid-cpp-tar-0.22-8.el6.noarch qpid-qmf-0.22-7.el6.i686 ruby-qpid-qmf-0.22-7.el6.i686 qpid-qmf-devel-0.22-7.el6.i686 python-qpid-qmf-0.22-7.el6.i686 qpid-cpp-server-ha-0.22-8.el6.i686 python-qpid-0.22-4.el6.noarch qpid-tests-0.22-4.el6.noarch qpid-cpp-client-devel-docs-0.22-8.el6.noarch qpid-snmpd-debuginfo-1.0.0-12.el6.i686 qpid-cpp-client-devel-0.22-8.el6.i686 qpid-cpp-server-devel-0.22-8.el6.i686 qpid-snmpd-1.0.0-12.el6.i686 perl-qpid-0.22-5.el6.i686 qpid-java-common-0.22-5.el6.noarch qpid-cpp-client-0.22-8.el6.i686 qpid-cpp-server-ssl-0.22-8.el6.i686 rh-qpid-cpp-tests-0.22-8.el6.i686 qpid-proton-c-0.4-2.2.el6.i686 qpid-proton-debuginfo-0.4-2.2.el6.i686 qpid-cpp-debuginfo-0.22-8.el6.i686 qpid-cpp-client-ssl-0.22-8.el6.i686 qpid-cpp-server-store-0.22-8.el6.i686 Not reproduced since it is a devel bug