Bug 874118

Summary: Deadlock in HA backup broker after disconnecting from primary
Product: Red Hat Enterprise MRG Reporter: Jason Dillaman <jdillama>
Component: qpid-cppAssignee: Alan Conway <aconway>
Status: CLOSED CURRENTRELEASE QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: unspecified Docs Contact:
Priority: medium    
Version: DevelopmentCC: aconway, esammons, jross, lzhaldyb, mcressma
Target Milestone: 2.3Keywords: OtherQA
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qpid-cpp-0.18-9 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 698367    

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
Comment 2 Alan Conway 2012-11-09 22:06:44 UTC 
    Committed fix:

    http://mrg1.lab.bos.redhat.com/cgit/qpid.git/commit/?h=0.18-mrg-aconway-ha-1&id=c3e72babca543297337b08f5bb1d8ed3ae53353e

    on branch http://mrg1.lab.bos.redhat.com/cgit/qpid.git/log/?h=0.18-mrg-aconway-ha-1 branched off 0.18-mrg