Back to bug 801605

Who When What Removed Added
Jason Dillaman 2012-03-08 23:38:07 UTC Summary Entire cluster crashes after client disconnects Entire cluster crashes after apparent re-establishment of federated link
Jason Dillaman 2012-03-08 23:38:39 UTC Blocks 698367
Justin Ross 2012-03-10 21:37:21 UTC Status NEW ASSIGNED
Assignee rhm-maint-list kgiusti
Target Milestone --- 2.2
Ted Ross 2012-03-15 14:48:39 UTC CC tross
Irina Boverman 2012-06-11 20:46:25 UTC Target Milestone 2.2 2.3
Jason Dillaman 2012-06-27 13:56:51 UTC Summary Entire cluster crashes after apparent re-establishment of federated link Non-responsive peer in federated link can result in entire cluster shutdown
Jason Dillaman 2012-07-12 17:01:55 UTC Link ID Apache JIRA 4133
Jason Dillaman 2012-07-12 18:17:44 UTC Link ID Apache JIRA 4133 Apache JIRA QPID-4133
Justin Ross 2012-11-14 20:54:42 UTC Keywords Patch
Priority unspecified high
Status ASSIGNED MODIFIED
Fixed In Version qpid-0.18
Assignee kgiusti aconway
Target Milestone 2.3 2.4
Justin Ross 2012-12-12 19:27:23 UTC Target Milestone 2.4 2.3
Leonid Zhaldybin 2012-12-13 15:34:37 UTC CC lzhaldyb
QA Contact mrgqe-bugs lzhaldyb
errata-xmlrpc 2013-01-07 19:37:54 UTC Status MODIFIED ON_QA
Leonid Zhaldybin 2013-01-08 09:55:51 UTC Status ON_QA VERIFIED
Jason Dillaman 2013-01-15 14:30:43 UTC Doc Text Cause: Federated links can issue cluster events prior to the link connection being fully established (protocol handshake complete).

Consequence: Cluster members receive event for unknown federated link connection which results in the members leaving the cluster.

Fix: Delay federated link IO processing until after the connection is fully established.

Result: Cluster members do not leave the cluster when federated to a non-responsive peer.
errata-xmlrpc 2013-03-06 01:01:16 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2013-03-06 18:55:19 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2013-03-06 13:55:19 UTC
John Skeoch 2014-11-09 22:38:29 UTC CC esammons

Back to bug 801605