Bug 710787 - Client doesn't completely honor reconnect=false Connection option
Summary: Client doesn't completely honor reconnect=false Connection option
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: 1.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 2.3
: ---
Assignee: Gordon Sim
QA Contact: Leonid Zhaldybin
URL:
Whiteboard:
Depends On:
Blocks: 698367
TreeView+ depends on / blocked
 
Reported: 2011-06-04 18:49 UTC by Andy Goldstein
Modified: 2014-11-09 22:38 UTC (History)
6 users (show)

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.
Clone Of:
Environment:
Last Closed: 2013-03-06 18:53:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Apache JIRA QPID-3292 0 None None None 2012-09-18 17:21:37 UTC
Red Hat Product Errata RHSA-2013:0561 0 normal SHIPPED_LIVE Moderate: Red Hat Enterprise MRG Messaging 2.3 security update 2013-03-06 23:48:13 UTC

Description Andy Goldstein 2011-06-04 18:49:25 UTC 
See https://issues.apache.org/jira/browse/QPID-3292 for details
Comment 1 Gordon Sim 2011-06-09 13:50:41 UTC 
Fixed upstream as http://svn.apache.org/viewvc?rev=1133822&view=rev
Comment 3 Leonid Zhaldybin 2012-10-09 10:52:24 UTC 
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
Comment 5 errata-xmlrpc 2013-03-06 18:53:43 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.