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

Bug 318816

Summary: [Legacy] Legacy mode is unreliable in multi-threaded environments
Product: [Modeling] EMF Reporter: Martin Fluegge <martin.fluegge>
Component: cdo.legacyAssignee: Christian Damus <give.a.damus>
Status: NEW --- QA Contact: Eike Stepper <stepper>
Severity: normal    
Priority: P3 CC: esteban.dugueperoux
Version: 4.13   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
Test v1 none

Description Martin Fluegge CLA 2010-07-04 10:16:54 EDT 
If multiple threads are accessing the same CDO resource (reading) both threads might influence each other. I am not yet sure whether this only occurs if the same object is read or if the whole resource is influenced. As a result values might be null. E.g If you have build a a containment tree with our NodeB test object it happens that when reading out the tree the name are 'null', although all objects are there. I am not even sure whether this only applies to EAttributes. 

Reproducibility: sometimes
Comment 1 Martin Fluegge CLA 2010-07-04 11:04:20 EDT 
Created attachment 173373 [details]
Test v1

This test makes the problem reproducible on Legacy/MemBranches, though I've seen it on Legacy/Mem, too.
Comment 2 Eike Stepper CLA 2012-06-05 07:29:55 EDT 
Moving all open bug reports to 4.1 because the release is very near and it's hghly unlikely that there will be spare time to address 4.0 problems.

Please make sure that your patches can be applied against the master branch and that your problem is not already fixed there!!!
Comment 3 Eike Stepper CLA 2012-08-14 22:57:44 EDT 
Moving all open issues to 4.2. Open bugs can be ported to 4.1 maintenance after they've been fixed in master.
Comment 4 Eike Stepper CLA 2013-06-03 05:54:04 EDT 
Hi Christian, I assign this legacy mode zilla to you, just in case you're ineterested. Don't feel obliged ;-)
Comment 5 Eike Stepper CLA 2013-06-29 12:19:06 EDT 
We'll try to address open problems in 4.3 (master) first and then port fixes back to 4.2.
Comment 6 Eike Stepper CLA 2015-07-14 02:21:30 EDT 
Moving all open bugzillas to 4.5.
Comment 7 Eike Stepper CLA 2016-07-31 01:04:16 EDT 
Moving all unaddressed bugzillas to 4.6.
Comment 8 Eike Stepper CLA 2017-12-28 01:15:28 EST 
Moving all open bugs to 4.7
Comment 9 Eike Stepper CLA 2019-11-08 02:07:41 EST 
Moving all unresolved issues to version 4.8-
Comment 10 Eike Stepper CLA 2019-12-13 12:54:35 EST 
Moving all unresolved issues to version 4.9
Comment 11 Eike Stepper CLA 2020-12-11 10:42:30 EST 
Moving to 4.13.