Red Hat Bugzilla – Bug 824985
Federated links become stale after source broker host fails
Last modified: 2014-09-24 11:04:16 EDT
Description of problem:
Create a federated link between source broker A to destination broker B (broker B is the client to broker A). Broker A will send heartbeats to broker B and broker B will send back heartbeats after it receives one from broker A.
If the broker A's host is hard-killed so that the TCP connection is not properly closed, broker B will continue to think it has an established connection to broker A. Since broker B does not send heartbeats and does not have a heartbeat timeout timer running, broker B never notices that the TCP link is stale.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a standard pull queue route from broker A (source) to broker B (destination)
2. Hard kill the host for broker A
Broker B's connection to broker A remains ESTABLISHED and does not recover.
Broker B's connection will be re-established.
Broker B's TCP connection to broker A will disconnect and it will attempt to reconnect to broker A or one of its failover nodes (in a clustered environment).
Fixed upstream at revision 1347044.
The fix works as expected.
Fix was tested on RHEL 5.9 and 6.4 on i686 and x86_64 architecture, with
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.