Bug 826684 - Recursive Event Generation Deadlock in Broker
Summary: Recursive Event Generation Deadlock in Broker
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: 2.1
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: ---
Assignee: Ken Giusti
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-30 18:40 UTC by Ted Ross
Modified: 2025-02-10 03:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:20:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
pstack from the broker process (115.63 KB, text/plain)
2012-05-30 18:42 UTC, Ted Ross 		no flags Details
View All

Description Ted Ross 2012-05-30 18:40:43 UTC 
Description of problem:

Deadlock occurred between two threads in the broker.  A queue message lock was involved so any other thread that tried to access that same queue also became locked.

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

qpid-cpp-0.14-16.el5

How reproducible:

Unknown - likely very rare

Steps to Reproduce:

No reproducer currently.
Comment 1 Ted Ross 2012-05-30 18:42:59 UTC 
Created attachment 587806 [details]
pstack from the broker process
Comment 2 Ted Ross 2012-05-30 18:44:52 UTC 
I'm assuming that the deadlock occurs between threads 1 and 18 in the pstack.
Comment 3 Red Hat Bugzilla 2025-02-10 03:20:00 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.
Note You need to log in before you can comment on or make changes to this bug.