Bug 847038 - Parallel federation connections may not recover on cluster failover.
Summary: Parallel federation connections may not recover on cluster failover.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: Development
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: 2.3.3
: ---
Assignee: Ken Giusti
QA Contact: Leonid Zhaldybin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-09 13:57 UTC by Ken Giusti
Modified: 2014-11-09 22:38 UTC (History)
5 users (show)

Fixed In Version: qpid-cpp-0.18-15
Doc Type: Bug Fix
Doc Text:
Cause: The cluster uses the endpoint IP address and port number to identify specific Federation Links on the broker. However, if two Links are created to the same destination, they will share the same IP address and port. This prevented the cluster from distinguishing between the two links. Consequence: Should a cluster failover occur, the cluster recovery code would erroneously interpret the two links as being only a single link, and the failover would fail - the Links would not be re-established properly. Fix: The cluster code was changed to use the Link's name parameter instead of the destination IP address and port. This name is always unique, regardless of destination. Result: The cluster code can now distinguish separate Links to the same destination. The Links are correctly restored should a failover event occur.
Clone Of:
Environment:
Last Closed: 2013-07-11 13:36:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1023 0 normal SHIPPED_LIVE Red Hat Enterprise MRG Messaging 2.3.3 update 2013-07-11 17:34:01 UTC

Description Ken Giusti 2012-08-09 13:57:03 UTC 
Description of problem:

  This problem only affects a "multi-link" federation configuration - that is, a broker that has two or more federation *connections* to the _same_ host.  At present, this configuration is only possible if manually set up using QMF (qpid-route does not support it).

  See upstream bug report:

  https://issues.apache.org/jira/browse/QPID-4193

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

How reproducible:

  Somewhat - usually will fail within 10-20 runs of the failover test.
  
Additional info:

  Upstream fix: http://svn.apache.org/viewvc?view=revision&revision=1370792
Comment 1 Justin Ross 2013-02-27 11:46:21 UTC 
Note, this appears to have gone into 0.19 before the queueing refactor.
Comment 7 Leonid Zhaldybin 2013-06-28 06:06:37 UTC 
Running the test_federation_multilink_failover unit test for several days on the latest available 2.3.3 packages did not trigger the issue.

Packages used for testing:

RHEL6.4
python-qpid-0.18-5.el6_4
python-qpid-qmf-0.18-18.el6_4
qpid-cpp-client-0.18-17.el6_4
qpid-cpp-client-devel-0.18-17.el6_4
qpid-cpp-client-devel-docs-0.18-17
qpid-cpp-server-0.18-17.el6_4
qpid-cpp-server-cluster-0.18-17.el6_4
qpid-cpp-server-devel-0.18-17.el6_4
qpid-cpp-server-store-0.18-17.el6_4
qpid-cpp-server-xml-0.18-17.el6_4
qpid-java-client-0.18-8.el6_4
qpid-java-common-0.18-8.el6_4
qpid-java-example-0.18-8.el6_4
qpid-jca-0.18-8.el6
qpid-jca-xarecovery-0.18-8.el6
qpid-qmf-0.18-18.el6_4
qpid-tests-0.18-2.el6
qpid-tools-0.18-10.el6_4
rh-qpid-cpp-tests-0.18-17.el6_4

RHEL5.9
python-qpid-0.18-5.el5_9
python-qpid-qmf-0.18-18.el5_9
qpid-cpp-client-0.18-17.el5_9
qpid-cpp-client-devel-0.18-17.el5_9
qpid-cpp-client-devel-docs-0.18-17.el5_9
qpid-cpp-client-ssl-0.18-17.el5_9
qpid-cpp-server-0.18-17.el5_9
qpid-cpp-server-cluster-0.18-17.el5_9
qpid-cpp-server-devel-0.18-17.el5_9
qpid-cpp-server-ssl-0.18-17.el5_9
qpid-cpp-server-store-0.18-17.el5_9
qpid-cpp-server-xml-0.18-17.el5_9
qpid-java-client-0.18-8.el5_9
qpid-java-common-0.18-8.el5_9
qpid-java-example-0.18-8.el5_9
qpid-jca-0.18-8.el5
qpid-jca-xarecovery-0.18-8.el5
qpid-qmf-0.18-18.el5_9
qpid-qmf-devel-0.18-18.el5_9
qpid-tools-0.18-10.el5_9
rh-qpid-cpp-tests-0.18-17.el5_9

This issue has been fixed. I'm moving bug to VERIFIED.
Comment 9 errata-xmlrpc 2013-07-11 13:36:23 UTC 
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.

http://rhn.redhat.com/errata/RHBA-2013-1023.html
Note You need to log in before you can comment on or make changes to this bug.