Bug 752510

Summary: Document optimal heartbeat timeouts
Product: Red Hat Enterprise MRG Reporter: Justin Ross <jross>
Component: Messaging_Programming_ReferenceAssignee: Alison Young <alyoung>
Status: CLOSED DUPLICATE QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.0CC: lbrindle, pmoravec
Target Milestone: 2.3   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 752491 Environment:
Last Closed: 2011-12-05 21:41:11 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: 752491    
Bug Blocks: 706388    

Description Justin Ross 2011-11-09 18:00:17 UTC 
+++ This bug was initially created as a clone of Bug #752491 +++

See https://bugzilla.redhat.com/show_bug.cgi?id=706388#c10

--- Additional comment from gsim on 2011-11-09 12:22:06 EST ---

As Pavel notes in https://issues.apache.org/jira/browse/QPID-3264, you want to ensure that heartbeats are "at most 1/2 of TCP retransmission overall-time (that by default around 15 minutes on Linux and 12 seconds on Windows)". This prevents the situation where the client gives up on the connection and yet the broker assumes it is still established.

A footnote to that effect could be added to the documentation in the appropriate places (e.g. table 2.4 in Programming Guide and section 7.3 in User Guide).

--- Additional comment from gsim on 2011-11-09 12:22:52 EST ---

Should this not be assigned to a documentation component now?
Comment 1 Lana Brindley 2011-12-05 21:41:11 UTC 

*** This bug has been marked as a duplicate of bug 752491 ***