Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 370297 - Possibility of a deadlock between merging collection into shared cache and IndirectList
Summary: Possibility of a deadlock between merging collection into shared cache and In...
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 413775 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-02-01 02:00 EST by Vikram Bhatia CLA
Modified: 2022-06-09 10:32 EDT (History)
1 user (show)

See Also:


Attachments
Proposed Fix (49.46 KB, patch)
2012-02-10 02:36 EST, Vikram Bhatia CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Vikram Bhatia CLA 2012-02-01 02:00:29 EST
There is a possibility of a deadlock while merging a collection into the shared cache and IndirectList when Vector is used.
Comment 1 Vikram Bhatia CLA 2012-02-01 02:07:51 EST
ContainerPolicy.mergeChanges() currently synchronize on target value or its delegate if instance of an IndirectCollection while merging the changes from the change set, i.e, removing and adding objects to the collection from the change set. This can cause a possible deadlock scenario while using native ORM if Vector is being used for the collection.
Comment 2 Vikram Bhatia CLA 2012-02-10 02:36:29 EST
Created attachment 210836 [details]
Proposed Fix
Comment 3 Vikram Bhatia CLA 2012-02-10 05:14:58 EST
Fixed in main trunk with r10833.
Comment 4 Lukas Jungmann CLA 2015-05-18 16:02:59 EDT
*** Bug 413775 has been marked as a duplicate of this bug. ***
Comment 5 Eclipse Webmaster CLA 2022-06-09 10:32:19 EDT
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink