Bug 1044003

Summary: setting heartbeat has no effect on connection establishment timeout
Product: Red Hat Enterprise MRG Reporter: Gordon Sim <gsim>
Component: python-qpidAssignee: Alan Conway <aconway>
Status: CLOSED CURRENTRELEASE QA Contact: Irina Boverman <iboverma>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 3.0CC: esammons, freznice, iboverma, jross
Target Milestone: 3.0Keywords: OtherQA, Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-qpid-0.22-10 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1044002 Environment:
Last Closed: 2015-01-21 12:52:22 UTC Type: Bug
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: 1044002    
Bug Blocks:    

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: