Kodo JDO Optimistic Locking Error
Author
Zhou Renjian
Create@
2004-11-18 09:28
kodo.util.OptimisticVerificationException: There was 1 optimistic locking error detected when flushing to the data store. This indicates that an object was concurrently modified in another transaction. The exception in the nested throwables array contains a failed object representing a concurrently modified object. Failed object id: [com.jozmas.wanote.db.INote-299]
NestedThrowables:
kodo.util.OptimisticVerificationException: An optimistic lock violation was detected when flushing object "com.jozmas.wanote.db.Catalog@5cc270" with id "com.jozmas.wanote.db.INote-299" to the data store. This indicates that the object was concurrently modified in another transaction.
FailedObject:com.jozmas.wanote.db.Catalog@5cc270
kodo.runtime.PersistenceManagerImpl.flushInternal(PersistenceManagerImpl.java:802)
kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:644)
kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:416)
com.jozmas.wanote.web.WebNewNote.createNoteWithParent(WebNewNote.java:112)
com.jozmas.wanote.web.WebNewNote.doPost(WebNewNote.java:81)
javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)