| Summary: | Client doesn't completely honor reconnect=false Connection option | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Andy Goldstein <agoldste> |
| Component: | qpid-cpp | Assignee: | Gordon Sim <gsim> |
| Status: | CLOSED ERRATA | QA Contact: | Leonid Zhaldybin <lzhaldyb> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 1.3 | CC: | esammons, gsim, iboverma, jross, lzhaldyb, tross |
| Target Milestone: | 2.3 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | qpid-cpp-0.18-1 | Doc Type: | Bug Fix |
| Doc Text: |
Cause:
The logic in the handling of loss of connection always resulted in at least on attempt to reconnect.
Consequence:
In the event that a client loses its connection to the broker, it would try once to reconnect even when the reconnect option was disabled.
Fix:
The logic in the handling of the loss of a connection was altered to distinguish it from opening a connection in the first place.
Result:
The reconnect option is now correctly handled; specifically if set to false there will never be a reconnect attempt made.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-03-06 18:53:43 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 698367 | ||
|
Description
Andy Goldstein
2011-06-04 18:49:25 UTC
Fixed upstream as http://svn.apache.org/viewvc?rev=1133822&view=rev Tested on RHEL5.8 and RHEL6.3 (both i386 and x86_64). C++ clients do not try to reconnect in case that 'reconnect' option is set to 'false'. Packages used for testing: RHEL5.8 qpid-cpp-client-0.18-1.el5 qpid-cpp-client-devel-0.18-1.el5 qpid-cpp-client-devel-docs-0.18-1.el5 qpid-cpp-client-rdma-0.18-1.el5 qpid-cpp-client-ssl-0.18-1.el5 qpid-cpp-mrg-debuginfo-0.18-1.el5 qpid-cpp-server-0.18-1.el5 qpid-cpp-server-cluster-0.18-1.el5 qpid-cpp-server-devel-0.18-1.el5 qpid-cpp-server-rdma-0.18-1.el5 qpid-cpp-server-ssl-0.18-1.el5 qpid-cpp-server-store-0.18-1.el5 qpid-cpp-server-xml-0.18-1.el5 RHEL6.3 qpid-cpp-client-0.18-1.el6_3 qpid-cpp-client-devel-0.18-1.el6_3 qpid-cpp-client-devel-docs-0.18-1.el6_3 qpid-cpp-client-rdma-0.18-1.el6_3 qpid-cpp-client-ssl-0.18-1.el6_3 qpid-cpp-debuginfo-0.18-1.el6_3 qpid-cpp-server-0.18-1.el6_3 qpid-cpp-server-cluster-0.18-1.el6_3 qpid-cpp-server-devel-0.18-1.el6_3 qpid-cpp-server-rdma-0.18-1.el6_3 qpid-cpp-server-ssl-0.18-1.el6_3 qpid-cpp-server-store-0.18-1.el6_3 qpid-cpp-server-xml-0.18-1.el6_3 -> 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/RHSA-2013-0561.html |