Bug 621998

Summary: hearbeats are broken
Product: Red Hat Enterprise MRG Reporter: Rafael H. Schloming <rafaels>
Component: python-qpidAssignee: Rafael H. Schloming <rafaels>
Status: CLOSED CURRENTRELEASE QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: high Docs Contact:
Priority: low    
Version: betaCC: jross, tross
Target Milestone: 1.3   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: python-qpid-0.7.946106-12 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-11 19:26:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Rafael H. Schloming 2010-08-06 18:00:55 UTC 
Description of problem:

The client blows up when heartbeats are enabled (i.e. when receiving a heartbeat from the server). Also the client doesn't actually check that heartbeats are received at the appropriate interval. This is problematic for reconnect since this is necessary to ensure that dead TCP connections are detected, something that is necessary for reconnect to function properly in all cases.

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

python-qpid-0.7.946106-11

How reproducible:

100%

Steps to Reproduce:

1. create a connection with the heartbeat parameter specified, e.g:

  conn = Connection(..., heartbeat=1)

2. wait for a heartbeat to arrive from the server (logging may be useful to verify that this is/has happened)
  
Actual results:

client blows up with an internal error


Expected results:

client should function normally