Community
Participate
Working Groups
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
I'd like to second this request: http://dev.eclipse.org/mhonarc/lists/eclipselink-dev/msg03939.html
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.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink