Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours
Bug 970166 - Deadlock detected during resources uninventory
Deadlock detected during resources uninventory
Status: NEW
Product: RHQ Project
Classification: Other
Component: CLI, Core Server, Database (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
Depends On:
  Show dependency treegraph
Reported: 2013-06-03 11:05 EDT by Filip Brychta
Modified: 2017-03-27 06:30 EDT (History)
2 users (show)

See Also:
Fixed In Version:
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)
postgresql log (101.07 KB, text/x-log)
2013-06-03 11:05 EDT, Filip Brychta
no flags Details
rhq server log (1.58 MB, text/x-log)
2013-06-03 11:06 EDT, Filip Brychta
no flags Details

  None (edit)
Description Filip Brychta 2013-06-03 11:05:46 EDT
Created attachment 756352 [details]
postgresql log

Description of problem:
At the end of our CLI test suite all resources are uninventorized. During this operation a deadlock was detected and exceptions were thrown to the rhq server log.

Version-Release number of selected component (if applicable):
Version: 4.8.0-SNAPSHOT
Build Number: 1231cc2

How reproducible:
3 out of 3

Additional info:
Resources are uninventorized following way:
Firstly we uninventory each platform's child one-by-one, then platform itself.

I attached complete rhq server log and postgresql log where you can find which statements cause the deadlock. Search for "deadlock detected"
Comment 1 Filip Brychta 2013-06-03 11:06:23 EDT
Created attachment 756353 [details]
rhq server log
Comment 2 jay 2017-03-27 06:30:32 EDT
Toward the finish of our CLI test suite all assets are uninventorized. Amid this operation a gridlock was recognized and special cases were tossed to the rhq server log.


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