Description of problem: It would be valuable to report error when unrecognized connection option is provided to the connection object, like c++ client do. Currently unrecognized options are silently ignored when creating the connection, so user may for example set the mistyped connection options in the API doc (see bug 959446), and won't be aware of that something went wrong. Version-Release number of selected component (if applicable): python-qpid-0.18-4 How reproducible: 100% Steps to Reproduce: 1. pass non-supported connection option to connection object 2. no error/warning appears Actual results: unrecognized connection options are silently ignored Expected results: An error reported on encountering unrecognized connection option Additional info:
Committed in upstream r1605704. To let automated tests passing, commit r1605703 is required.
Python client correctly throws an exception, when incorrect connection option is passed to Connection object. qpid.messaging.exceptions.ConnectionError: None(Unknown connection option bla with value asda) Verified on python-qpid-0.30-2.el6
(In reply to Petr Matousek from comment #0) > Description of problem: > > It would be valuable to report error when unrecognized connection option is > provided to the connection object, like c++ client do. > > Currently unrecognized options are silently ignored when creating the > connection, so user may for example set the mistyped connection options in > the API doc (see bug 959446), and won't be aware of that something went > wrong. > > Version-Release number of selected component (if applicable): > python-qpid-0.18-4 > > How reproducible: > 100% > > Steps to Reproduce: > 1. pass non-supported connection option to connection object > 2. no error/warning appears > > Actual results: > unrecognized connection options are silently ignored > > Expected results: > An error reported on encountering unrecognized connection option > > Additional info: Noted that the API doc was fixed a while back. Nothing for a customer to configure here, so no Release Note required.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2015-0805.html