Description of problem: The qpid::messaging API can throw qpid::Exception whereas it should only throw subtypes of qpid::types::Exception. Version-Release number of selected component (if applicable): Since qpid-0.20 (my AMQP 1.0 work introduced the problem) How reproducible: 100% Steps to Reproduce: 1. try to set connection options to include 'protocol:wrong' Actual results: Get an qpid::Exception thrown Expected results: Get some subclass of qpid::types::Exception thrown, e.g. qpid::messaging::MessagingException. Additional info:
Fixed upstream: https://svn.apache.org/r1528082
This issue was tested on RHEL 6.5 i686 and x86_64 with packages: perl-qpid-0.22-7.el6 python-qpid-0.22-10.el6 python-qpid-qmf-0.22-26.el6 qpid-cpp-client-0.22-33.el6 qpid-cpp-client-devel-0.22-33.el6 qpid-cpp-client-devel-docs-0.22-33.el6 qpid-cpp-client-ssl-0.22-33.el6 qpid-cpp-server-0.22-33.el6 qpid-cpp-server-devel-0.22-33.el6 qpid-cpp-server-ha-0.22-33.el6 qpid-cpp-server-ssl-0.22-33.el6 qpid-cpp-server-store-0.22-33.el6 qpid-cpp-server-xml-0.22-33.el6 qpid-java-client-0.22-5.el6 qpid-java-common-0.22-5.el6 qpid-java-example-0.22-5.el6 qpid-jca-0.22-1.el6 qpid-jca-xarecovery-0.22-1.el6 qpid-proton-c-0.6-1.el6 qpid-proton-c-devel-0.6-1.el6 qpid-qmf-0.22-26.el6 qpid-snmpd-1.0.0-15.el6 qpid-tools-0.22-7.el6 ruby-qpid-qmf-0.22-26.el6 fix works as expected.