kodo.util.OptimisticVerificationException: An optimistic lock violation was detected when flushing object instance "com.myapp.MyObject-17998021794883:18001095407305" to the data store. This indicates that the object was concurrently modified in another transaction.[com.myapp.MyObject-17998021794883:18001095407305]

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 3004, 1 year ago
An optimistic lock violation was detected when flushing object instance "com.myapp.MyObject-17998021794883:18001095407305" to the data store. This indicates that the object was concurrently modified in another transaction.[com.myapp.MyObject-17998021794883:18001095407305]
via Oracle Community by 3004, 1 year ago
An optimistic lock violation was detected when flushing object instance "com.elaxy.service.product.jdoimpl.BEProductPO-26477" to the data store. This indicates that the object was concurrently modified in another transaction.[com.elaxy.service.product.jdoimpl.BEProductPO-26477]
via Oracle Community by 3004, 1 year ago
An optimistic lock violation was detected when flushing object "customer.model.Customer@146c2f2" 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@146c2f2
via Oracle Community by 3004, 1 year ago
An optimistic lock violation was detected when flushing object "co m.attws.stress.jdo.SubGadget@10d16b" with id "com.attws.stress.jdo.Gadget-5021" to the data store. This indicates that the object was concurrently modified in another transaction. FailedObject:com.attws.stress.jdo.SubGadget@10d16b
kodo.util.OptimisticVerificationException: An optimistic lock violation was detected when flushing object instance "com.myapp.MyObject-17998021794883:18001095407305" to the data store. This indicates that the object was concurrently modified in another transaction.[com.myapp.MyObject-17998021794883:18001095407305]
at kodo.jdbc.runtime.PreparedStatementManager.checkUpdate(PreparedStatementManager.java:359)
at kodo.jdbc.runtime.PreparedStatementManager.flushInternal(PreparedStatementManager.java:235)
at kodo.jdbc.runtime.PreparedStatementManager.flushInternal(PreparedStatementManager.java:133)
at kodo.jdbc.runtime.PreparedStatementManager.flush(PreparedStatementManager.java:84)
at kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:445)
at kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:217)
at kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:95)
at kodo.jdbc.runtime.JDBCStoreManager.flush(JDBCStoreManager.java:614)
at kodo.runtime.DelegatingStoreManager.flush(DelegatingStoreManager.java:153)
at kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:1159)
at kodo.runtime.PersistenceManagerImpl.flushSafe(PersistenceManagerImpl.java:1042)
at kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:969)
at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010)
at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115)
at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1216)
at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1990)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:275)
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)

Users with the same issue

You are the first who have seen this exception.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.