Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 338504 - Deadlock in CollectionMapping while merging changes during transaction rollback
Summary: Deadlock in CollectionMapping while merging changes during transaction rollback
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: David Minsky CLA
QA Contact: Project Inbox CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-01 01:33 EST by Vikram Bhatia CLA
Modified: 2022-06-09 10:15 EDT (History)
1 user (show)

See Also:


Attachments
Probable Fix (10.03 KB, patch)
2011-03-01 01:51 EST, Vikram Bhatia CLA
david.minsky: iplog+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
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