Bug 720714 - Clustered broker exits with invalid-argument error after attempting to create dynamic federation bridge
Summary: Clustered broker exits with invalid-argument error after attempting to create...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: 1.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 2.3
: ---
Assignee: Ken Giusti
QA Contact: Leonid Zhaldybin
URL:
Whiteboard:
Depends On:
Blocks: 698367 803771
TreeView+ depends on / blocked
 
Reported: 2011-07-12 15:13 UTC by Jason Dillaman
Modified: 2014-11-09 22:38 UTC (History)
5 users (show)

Fixed In Version: qpid-cpp-0.18-1
Doc Type: Bug Fix
Doc Text:
Cause: The mechanism for generating Link and Bridge names was incorrect and could generate the same name for multiple distinct Links and Bridges. Consequence: The broker's internal federation configuration would become corrupt. This resulted in inconsistencies among clustered brokers, forcing one or more brokers to exit. Fix: Fix the Bridge and Link naming algorithm to guarantee unique names for all Bridge and Link objects. Result: Clustered brokers running federation would remain consistent.
Clone Of:
Environment:
Last Closed: 2013-03-06 18:53:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Log from failed clustered broker (3.78 KB, text/plain)
2011-07-12 15:13 UTC, Jason Dillaman 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Apache JIRA QPID-3773 0 None None None Never
Red Hat Product Errata RHSA-2013:0561 0 normal SHIPPED_LIVE Moderate: Red Hat Enterprise MRG Messaging 2.3 security update 2013-03-06 23:48:13 UTC

Description Jason Dillaman 2011-07-12 15:13:21 UTC 
Description of problem:
While starting up a broker cluster node, the broker occasionally exits with an invalid-argument exception.  The broker startup logic for each cluster member attempts to create a dynamic federation bridge to another cluster of brokers.  It appears that a session error caused by attempting to obtain an exclusive lock on the bridge queue might cause an inconsistency in the broker.

Version-Release number of selected component (if applicable):
qpid-cpp-server-0.7.946106-28_ptc_hotfix_5_v2.el5
qpid-cpp-server-cluster-0.7.946106-28_ptc_hotfix_5_v2.el5

How reproducible:
Fairly often right at broker start-up.

Steps to Reproduce:
1. Start the first clustered broker and create a dynamic federation bridge to another broker.
2. Start the second cluster broker and attempt to create the same dynamic federation bridge.
  
Actual results:
A cluster member fails.

Expected results:
All cluster members remain functional.

Additional info:
Comment 1 Jason Dillaman 2011-07-12 15:13:55 UTC 
Created attachment 512453 [details]
Log from failed clustered broker
Comment 4 Justin Ross 2012-04-10 18:52:05 UTC 
https://issues.apache.org/jira/browse/QPID-3773
Comment 9 Leonid Zhaldybin 2013-01-09 11:13:24 UTC 
Tested on RHEL5.9 and RHEL6.3 (both i386 and x86_64). This issue has been fixed.

Packages used for testing:

RHEL5.9
qpid-cpp-client-0.18-13.el5
qpid-cpp-client-devel-0.18-13.el5
qpid-cpp-client-devel-docs-0.18-13.el5
qpid-cpp-client-ssl-0.18-13.el5
qpid-cpp-server-0.18-13.el5
qpid-cpp-server-cluster-0.18-13.el5
qpid-cpp-server-devel-0.18-13.el5
qpid-cpp-server-ssl-0.18-13.el5
qpid-cpp-server-store-0.18-13.el5
qpid-cpp-server-xml-0.18-13.el5
qpid-java-client-0.18-6.el5
qpid-java-common-0.18-6.el5
qpid-java-example-0.18-6.el5
qpid-qmf-0.18-13.el5
qpid-qmf-devel-0.18-13.el5
qpid-tools-0.18-7.el5

RHEL6.3
qpid-cpp-client-0.18-13.el6
qpid-cpp-client-devel-0.18-13.el6
qpid-cpp-client-devel-docs-0.18-13.el6
qpid-cpp-server-0.18-13.el6
qpid-cpp-server-devel-0.18-13.el6
qpid-cpp-server-store-0.18-13.el6
qpid-cpp-server-xml-0.18-13.el6
qpid-java-client-0.18-6.el6
qpid-java-common-0.18-6.el6
qpid-java-example-0.18-6.el6
qpid-qmf-0.18-13.el6
qpid-tools-0.18-7.el6_3

-> VERIFIED
Comment 11 errata-xmlrpc 2013-03-06 18:53:46 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/RHSA-2013-0561.html
Note You need to log in before you can comment on or make changes to this bug.