| Summary: | Possibility of a deadlock between merging collection into shared cache and IndirectList | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Vikram Bhatia <vikram.jeet.bhatia> | ||||
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | michaelnielson | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Vikram Bhatia
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. Created attachment 210836 [details]
Proposed Fix
Fixed in main trunk with r10833. *** Bug 413775 has been marked as a duplicate of this bug. *** The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |