Re: [eclipselink-users] Weird exception thrown by EL 2.1.2

[Rohit Banga <rohit.banga@xxxxxxxxxx>]

Hi Michael

There is some documentation about OptimisticLockException here.
http://wiki.eclipse.org/Using_Advanced_Unit_of_Work_API_%28ELUG%29#How_to_Force_a_Version_Field_Update

You can see if in your architecture you are having multiple client sessions modifying the same object.

Thanks
Rohit

On 2/25/2011 8:38 PM, Michael Simons wrote:

Hi,

 

we get the following exception

Exception Description: The object [net.uniopt.domain.actual.ActualOrderStop@11ea9] cannot be deleted because it has changed or been deleted since it was last read.

Class> net.uniopt.domain.actual.ActualOrderStop Primary Key> 73.385

javax.persistence.RollbackException: javax.persistence.OptimisticLockException: Exception [EclipseLink-5003] (Eclipse Persistence Services - 2.1.2.v20101206-r8635): org.eclipse.persistence.exceptions.OptimisticLockException

Exception Description: The object [net.uniopt.domain.actual.ActualOrderStop@11ea9] cannot be deleted because it has changed or been deleted since it was last read.

Class> net.uniopt.domain.actual.ActualOrderStop Primary Key> 73.385

      at org.eclipse.persistence.internal.jpa.transaction.EntityTransactionImpl.commitInternal(EntityTransactionImpl.java:102)

 

But the version-field of the object is 1, in the database as in the program.

 

Does anybody know what might cause this misapprehension?

 

Kind Regards, Michael

 

_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users

--
Thanks and Regards
Rohit Banga
Member Technical Staff
Oracle Server Technologies