Bug 874118 - Deadlock in HA backup broker after disconnecting from primary
Deadlock in HA backup broker after disconnecting from primary
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp (Show other bugs)
Unspecified Unspecified
medium Severity unspecified
: 2.3
: ---
Assigned To: Alan Conway
MRG Quality Engineering
: OtherQA
Depends On:
Blocks: 698367
  Show dependency treegraph
Reported: 2012-11-07 09:45 EST by Jason Dillaman
Modified: 2013-03-19 12:41 EDT (History)
5 users (show)

See Also:
Fixed In Version: qpid-cpp-0.18-9
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jason Dillaman 2012-11-07 09:45:08 EST
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:

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

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.