Description of problem: The connection option syntax is subtly different between the language bindings. For example, to set the reconnect limit, the syntax is the following: in C++: reconnect-limit in Python: reconnect_limit The documentation uses the Python syntax but does not call out the C++ differences. To compound the problem, unrecognized options in C++ are silently ignored. If a user chooses the wrong syntax (as he would do if he read the documentation), the option does not take effect and the default is used instead, leading to unpredictable and undesired results. At the very least, the documentation needs to be enhanced to clarify this issue. A better solution would be to make the syntax the same in all languages. If there are characters that are illegal in certain languages, those characters should be avoided.
*** Bug 659322 has been marked as a duplicate of this bug. ***
Tracked upstream as https://issues.apache.org/jira/browse/QPID-3115
Fixed upstream on trunk in http://svn.apache.org/viewvc?view=rev&rev=1078075, http://svn.apache.org/viewvc?view=rev&rev=1078733 and http://svn.apache.org/viewvc?view=rev&rev=1078743. Merged to 0.10 release branch http://svn.apache.org/viewvc?rev=1078823&view=rev.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: C++ client used hyphen rather than underscore in connection option names (e.g. reconnect-interval rather than reconnect_interval). It also silently ignored options it did not recognise. Consequence: Option names were different from those used in python, and incorrect options were hard to spot as the client silently ignored them. Fix: Client now recognises both old names and the python equivalents for consistency. It also throws an exception if an unrecognised option is encountered. Result: More consistency; easier to spot errors.
The issue has been fixed. Verified on RHEL6.4 (i386, x86_64) packages installed: qpid-cpp-*-0.22-10 -> VERIFIED
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. http://rhn.redhat.com/errata/RHEA-2014-1296.html