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

Bug 328799

Summary:	CommitNotifications overtaking each other
Product:	[Modeling] EMF	Reporter:	Eike Stepper <stepper>
Component:	cdo.core	Assignee:	Eike Stepper <stepper>
Status:	CLOSED WONTFIX	QA Contact:	Eike Stepper <stepper>
Severity:	normal
Priority:	P3
Version:	3.0
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Eike Stepper

2010-10-27 04:33:39 EDT

Cloned from: 328352: CommitNotifications overtaking each other
https://bugs.eclipse.org/bugs/show_bug.cgi?id=328352

I noticed that the CommitNotifications seem to be able to overtake each other when there are many commits (for the same object & feature) done quickly after each other. This is also the cause for bug #312404 (for which a workaround has been added). The problem is not only present in the CommitRunnables on the RepositorySynchronizer, but also in normal InvalidationRunnables (see screenshot), which might lead to IndexOutOfBoundsExceptions on the view or changes applied in wrong order.

The problem is probably not limited to CommitNotifications and might not a bug but a feature of Net4J, so I'm unsure if this should be fixed at Net4J level.

Comment 1 Eike Stepper

2010-10-27 05:42:58 EDT

Unfortunately the fix depends on https://bugs.eclipse.org/bugs/attachment.cgi?id=181595 and that one is definitely incompatible with R3_0_maintenance ;-(