kodo.util.OptimisticVerificationException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Optimistic mode
    via by 3004,
    • kodo.util.OptimisticVerificationException: An optimistic lock violation was detected when flushing object "com.attws.str ess.jdo.SubGadget@110c2e8" with id "com.attws.stress.jdo.Gadget-5023" to the data store. This indicates that the object was concurrently modified in another transaction. FailedObject:com.attws.stress.jdo.SubGadget@110c2e8 at kodo.runtime.PersistenceManagerImpl.flushInternal(PersistenceManagerImpl.java:774) at kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:639) at kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69) at kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:411) at com.attws.stress.jdo.JdoInvoker.invoke(JdoInvoker.java:53) at com.attws.stress.ClientThread.run(ClientThread.java:37) Caused by: kodo.util.OptimisticVerificationException: 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 at kodo.jdbc.runtime.PreparedStatementManager.checkUpdate(PreparedStatementManager.java:247) at kodo.jdbc.runtime.PreparedStatementManager.flush(PreparedStatementManager.java:200) at kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:170) at kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:71) at kodo.jdbc.runtime.JDBCStoreManager.flush(JDBCStoreManager.java:503) at kodo.runtime.DelegatingStoreManager.flush(DelegatingStoreManager.java:158) at kodo.runtime.PersistenceManagerImpl.flushInternal(PersistenceManagerImpl.java:760) ... 5 more
    No Bugmate found.