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

Bug 318292

Summary:	default of "eclipselink.order-updates" property
Product:	z_Archived	Reporter:	Bernhard.Riedhofer
Component:	Eclipselink	Assignee:	Nobody - feel free to take it <nobody>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	adrian.goerler, gordon.yorke, SebTardif
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
See Also:	https://bugs.eclipse.org/bugs/show_bug.cgi?id=304738
Whiteboard:

Description Bernhard.Riedhofer

2010-06-29 06:55:10 EDT

Build Identifier: 2.0

The default of the order-updates property should be true for the following reasons:

I searched a longer time for the reason why implicit rollbacks occured on the database and why deadlocks happened on the database. Probably there are other customers which were facing the same issue and wasted some time to figure out what happened. Additionally with the SPECjEnterprise 2010 benchmark I didn't saw degradation in CPU utilization when switching from the default "false" to "true" (inbetween measurement inacuracy of <1%). However performance should be second to correctness.

Reproducible: Always

Comment 1 Adrian Goerler

2010-06-29 07:37:37 EDT

I'd like to second this request:

http://dev.eclipse.org/mhonarc/lists/eclipselink-dev/msg03939.html

Comment 2 Gordon Yorke

2010-06-29 15:48:53 EDT

As mentioned in the referenced thread EclipseLink does generally order updates and any ordering issues are unlikely.  

I am going to close this bug as WONTFIX but please continue to lobby for this bug and encourage others vote for it if it applies to them.

Comment 3 Eclipse Webmaster

2022-06-09 10:31:10 EDT

The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink