kodo.util.OptimisticVerificationException

Optimistic locking errors were detected when flushing to the data store. This indicates that some objects were concurrently modified in another transaction. Failed objects: [...] [java.util.ArrayList]]

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web24

  • via Oracle Community by 3004, 11 months ago
    Optimistic locking errors were detected when flushing to the data store. This indicates that some objects were concurrently modified in another transaction. Failed objects: [model.WfMessageQueue@1b2b10a] [java.util.ArrayList]
  • via Oracle Community by 3004, 11 months ago
    Optimistic locking errors were detected when flushing to the data store. This indicates that some objects were concurrently modified in another transaction. Failed objects: [...] [java.util.ArrayList]]
  • via Oracle Community by 3004, 11 months ago
    An optimistic lock violation was detected when flushing object "customer.model.Customer@d67b44" with id "customer.model.Customer-99" to the data store. This indicates that the object was concurrently modified in another transaction. FailedObject:customer.model.Customer@d67b44
  • Stack trace

    • kodo.util.OptimisticVerificationException: Optimistic locking errors were detected when flushing to the data store. This indicates that some objects were concurrently modified in another transaction. Failed objects: [...] [java.util.ArrayList]] at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1683) at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:325) at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:246) at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:299) at weblogic.ejb20.internal.StatelessEJBObject.postInvoke(StatelessEJBObject.java:140) at com.myapp.DataAccess_55rfae_EOImpl.commit(DataAccess_55rfae_EOImpl.java:523) at com.myapp.DataAccess_55rfae_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477) at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415) at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.