Bug 727904 - Deadlock when trying to delete a group.
Deadlock when trying to delete a group.
Status: NEW
Product: RHQ Project
Classification: Other
Component: Core Server (Show other bugs)
Unspecified Unspecified
high Severity unspecified (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
Depends On:
Blocks: rhq41
  Show dependency treegraph
Reported: 2011-08-03 11:18 EDT by Robert Buck
Modified: 2011-08-30 10:47 EDT (History)
1 user (show)

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

Attachments (Terms of Use)
Stack trace showing deadlock (4.20 KB, text/plain)
2011-08-03 11:18 EDT, Robert Buck
no flags Details

  None (edit)
Description Robert Buck 2011-08-03 11:18:08 EDT
Description of problem:

In the perf environment, which has lots of resources (perhaps related) after I created a group (either compatible or mixed), I got a deadlock and stack trace showing up in the UI.

How reproducible:


Steps to Reproduce:
1. Create a couple groups when lots of resources exist.
2. Delete them

Actual results:

Exception then stack trace in Message Center.
Comment 1 Robert Buck 2011-08-03 11:18:55 EDT
Created attachment 516536 [details]
Stack trace showing deadlock
Comment 2 Charles Crouch 2011-08-11 07:53:48 EDT
Bob, can you still replicate this in the new perf env?
Comment 3 Robert Buck 2011-08-11 10:11:50 EDT
Charles, not presently; first of all, we have scaled back the perf environment, and we cleaned up oracle by recreating the oracle user/schema. After all the cleanup, everything was noticeably snappier. I'd like to keep this one open, as low priority, or close it as not reproducible. At least having the record of its occurrence is useful.
Comment 4 Charles Crouch 2011-08-11 23:47:31 EDT
Go ahead and prioritize/close as you see fit

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