Bug 825331

Summary:	Deadlock in plugin container (possible issue with resource hierarchy traversal)
Product:	[Other] RHQ Project	Reporter:	Jay Shaughnessy <jshaughn>
Component:	Agent, Plugin Container	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mike Foley <mfoley>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.4	CC:	hrupp, jsanda
Target Milestone:	---
Target Release:	JON 3.1.0
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	823942	Environment:
Last Closed:	2013-09-04 09:10:37 UTC	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:	823942
Bug Blocks:	782579

Description Jay Shaughnessy 2012-05-25 17:35:35 UTC

+++ This bug was initially created as a clone of Bug #823942 +++

Deadlock detected in PC while testing with AS7 inventory.  Agent log and thread dump attached.

Notes:
- Async avail checking may have been turned on

Comment 1 Jay Shaughnessy 2012-05-25 17:41:02 UTC

release/jon3.1.x 
commit 9e0b16da140dce49c187aec4ac786b45e6573f82
    [823942] Prefer resource container Resource when recursing hierarchy
    Given recent optimizations it's necessary to use the ResourceContainer's
    version of a resource when requiring the most up to date version of
    the resource.  This commit ensures that when walking the hierarchy we
    prefer the container's version of the resource when getting children.
    (cherry picked from commit 14d53ea73b219a85d1b54584457ed48a60e1a556)

commit e8dcb395feaa2ae567521ee4ebfb0de5765103e7    
    (fix conflict in MeasurementManager that I missed when I committed 9e0b16da1)

commit a01bc1b1fa16b21872ae99242d14d18a7fc29b6a
    [823942] Update test code related to fixes for this issue.
    (cherry picked from commit 5c91b4659d17ec66c01260dfa3339d182558702b)

Comment 2 Heiko W. Rupp 2013-09-04 09:10:37 UTC

Closing as it has been implemented and is in production for a long time.