kodo.util.OptimisticVerificationException: 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]

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

Samebug tips

Do you know how to solve this issue? Write a tip to help other users and build your expert profile.

Solutions on the web

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 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 "customer.model.Customer@1095fd7" 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@1095fd7
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.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]
at kodo.jdbc.runtime.PreparedStatementManager.checkUpdate(PreparedStatementManager.java:401)
at kodo.jdbc.runtime.PreparedStatementManager.flushInternal(PreparedStatementManager.java:237)
at kodo.jdbc.runtime.PreparedStatementManager.flush(PreparedStatementManager.java:206)
at kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:292)
at kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:116)
at kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:95)
at kodo.jdbc.runtime.JDBCStoreManager.flush(JDBCStoreManager.java:609)
at kodo.runtime.DelegatingStoreManager.flush(DelegatingStoreManager.java:153)
at kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:1385)
at kodo.runtime.PersistenceManagerImpl.flushSafe(PersistenceManagerImpl.java:1266)
at kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:1193)
at kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
at kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:646)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Write tip

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