Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 338504

Summary: Deadlock in CollectionMapping while merging changes during transaction rollback
Product: z_Archived Reporter: Vikram Bhatia <vikram.jeet.bhatia>
Component: EclipselinkAssignee: David Minsky <david.minsky>
Status: RESOLVED FIXED QA Contact: Project Inbox <eclipselink.foundation-inbox>
Severity: normal    
Priority: P3 CC: david.minsky
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:
Attachments:
Description Flags
Probable Fix david.minsky: iplog+

Description Vikram Bhatia CLA 2011-03-01 01:33:16 EST 
Build Identifier: 

While merging the object from original to working copy in case transaction is rolled back, source object is iterated and mergeChanges() is called after synchronizing on original object which can possibly result in a deadlock. 

Instead of synchronizing on original object, it should be cloned and used while merging changes from original object to working copy.



Reproducible: Sometimes

Steps to Reproduce:
Reproducer not available. It is intermittent problem and difficult to reproduce.
Comment 1 Vikram Bhatia CLA 2011-03-01 01:51:36 EST 
Created attachment 190022 [details]
Probable Fix
Comment 2 David Minsky CLA 2011-03-03 16:15:19 EST 
Checked into revision: 9071 (2.3 - trunk)
Reviewed: Gordon Yorke
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:08:43 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
Comment 4 Eclipse Webmaster CLA 2022-06-09 10:15:36 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink