| Re: [eclipselink-users] Weird exception thrown by EL 2.1.2 |
Hi, sorry for taking your time. A database trigger was causing the behaviour. Kind Regards, Michael Von: eclipselink-users-bounces@xxxxxxxxxxx [mailto:eclipselink-users-bounces@xxxxxxxxxxx] Im Auftrag von Michael Simons 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 |