Bug 874118 - Deadlock in HA backup broker after disconnecting from primary
Summary: Deadlock in HA backup broker after disconnecting from primary
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: Development
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: 2.3
: ---
Assignee: Alan Conway
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks: 698367
TreeView+ depends on / blocked
 
Reported: 2012-11-07 14:45 UTC by Jason Dillaman
Modified: 2013-03-19 16:41 UTC (History)
5 users (show)

Fixed In Version: qpid-cpp-0.18-9
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jason Dillaman 2012-11-07 14:45:08 UTC
Description of problem:
After a backup disconnects from a primary, it will attempt to destroy any auto-delete queues.  However, if an auto-delete queue has a timeout of zero seconds set, the HA broker will deadlock holding a reader lock to the exchange registry while attempting to acquire a writer lock.

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

How reproducible:
100%

Steps to Reproduce:
1. Create an auto-delete queue w/ an auto-delete timeout of zero seconds
2. Disconnect the backup from the primary
  
Actual results:
The backup broker deadlocks

Expected results:
The backup broker does not deadlock

Workaround:
Never set the auto-delete timeout attribute if the timeout is zero seconds


Note You need to log in before you can comment on or make changes to this bug.