Bug 1044003 - setting heartbeat has no effect on connection establishment timeout
Summary: setting heartbeat has no effect on connection establishment timeout
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: python-qpid
Version: 3.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: 3.0
: ---
Assignee: Alan Conway
QA Contact: Irina Boverman
URL:
Whiteboard:
Depends On: 1044002
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-17 15:27 UTC by Gordon Sim
Modified: 2015-01-21 12:52 UTC (History)
4 users (show)

Fixed In Version: python-qpid-0.22-10
Doc Type: Bug Fix
Doc Text:
Clone Of: 1044002
Environment:
Last Closed: 2015-01-21 12:52:22 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Apache JIRA QPID-5428 0 None None None Never

Description Gordon Sim 2013-12-17 15:27:52 UTC
+++ This bug was initially created as a clone of Bug #1044002 +++

Description of problem:

The python client only uses heartbeats once the connection has been established. It does not use them to time out the initial connect attempt.

E.g. modify drain to use a 5sec heartbeat, start a broker, run drain -f amq.direct and then kill -STOP the broker - heartbeats are missed and connection times out as expected.

But now try to reconnect to the hung broker, and the connect attempt will not timeout.

Version-Release number of selected component (if applicable):

2.3 and before as well as 3.0 early access

How reproducible:

100%

Steps to Reproduce:
1. modify drain to use a 5sec heartbeat
2. start a broker
3. drain -f amq.direct
4. kill -STOP the broker
5. restart drain -f amq.direct

Actual results:

heartbeat times out the drain in step 3 but not in step 5, where it hangs

Expected results:

In both step 3 and 5 drain exits with timeout after 10 seconds

Additional info:


Note You need to log in before you can comment on or make changes to this bug.