OptimisticVerificationException

Question

I am getting the following error:
kodo.util.OptimisticVerificationException: An optimistic lock violation
was detected when flushing object
"com.xyz.packagemerge.model.Package@6bfc1ff8" with id
"com.xyz.packagemerge.model.Package-57368" to the data store. This
indicates that the object was concurrently modified in another transaction.
FailedObject:com.xyz.packagemerge.model.Package@6bfc1ff8
     at
kodo.jdbc.runtime.PreparedStatementManager.checkUpdate(PreparedStatementManager.java(Compiled
Code))
     at
kodo.jdbc.runtime.PreparedStatementManager.flushInternal(PreparedStatementManager.java(Compiled
Code))
     at
kodo.jdbc.runtime.PreparedStatementManager.flush(PreparedStatementManager.java(Inlined
Compiled Code))
     at
kodo.jdbc.runtime.PreparedStatementManager.flush(PreparedStatementManager.java(Compiled
Code))
I have tried every thing I can find, and the only solution that has worked
was to remove the jdbc-version-ind from the mapping files. This solution
is undesirable in addition to being unacceptable due to the performance
degradation it causes (10 - 50 times increase in processing time).
The application is single threaded, there is only 1 persistence manager,
and there are no other transactions (or even connnections) to the database.
Relevant configuration info:
[Thread-20] kodo.jdbc.JDBC - Using dictionary class
"kodo.jdbc.sql.OracleDictionary" (Oracle Oracle9i Enterprise Edition
Release 9.2.0.5.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.5.0 - Production ,Oracle JDBC driver 9.0.1.0.0).
javax.jdo.option.ConnectionDriverName=oracle.jdbc.driver.OracleDriver
javax.jdo.PersistenceManagerFactoryClass=kodo.jdbc.runtime.JDBCPersistenceManagerFactory
javax.jdo.option.Multithreaded=false
javax.jdo.option.NontransactionalWrite=false
javax.jdo.option.NontransactionalRead=false
javax.jdo.option.RetainValues=false
javax.jdo.option.RestoreValues=false
kodo.ConnectionFactoryProperties=(MaxActive\=5)
kodo.jdbc.DBDictionary=oracle(StoreCharsAsNumbers\=false, BatchLimit\=0)
kodo.DataCache=true(CacheSize\=5000)
kodo.RemoteCommitProvider=sjvm
kodo.QueryCache=true(CacheSize\=1000)
It appears that it could be a problem with the state-image not recognizing
the difference between null and empty string, or an inconsistency in the
data cache.

Answer 1

Clint-
Can you disable batch updates and see if it works? There are known
problems with some versions of the Oracle JDBC driver (including the one
you are using) that prevents incorrect update counts from being returned
from batch updates; the most common symptom of this problem is an
incorrect OptimisticVerificationException being thrown.
You should also try using version 9.0.1.0.0 of the Oracle driver,
which is known to work much better for batch updating.
Finally, what version of Kodo are you using? Recent versions (3.1.4)
should have detected this problem and issued a warning.
In article <[email protected]>, Clint LeGros wrote:
I am getting the following error:
kodo.util.OptimisticVerificationException: An optimistic lock violation
was detected when flushing object
"com.xyz.packagemerge.model.Package@6bfc1ff8" with id
"com.xyz.packagemerge.model.Package-57368" to the data store. This
indicates that the object was concurrently modified in another transaction.
FailedObject:com.xyz.packagemerge.model.Package@6bfc1ff8
     at
kodo.jdbc.runtime.PreparedStatementManager.checkUpdate(PreparedStatementManager.java(Compiled
Code))
     at
kodo.jdbc.runtime.PreparedStatementManager.flushInternal(PreparedStatementManager.java(Compiled
Code))
     at
kodo.jdbc.runtime.PreparedStatementManager.flush(PreparedStatementManager.java(Inlined
Compiled Code))
     at
kodo.jdbc.runtime.PreparedStatementManager.flush(PreparedStatementManager.java(Compiled
Code))
I have tried every thing I can find, and the only solution that has worked
was to remove the jdbc-version-ind from the mapping files. This solution
is undesirable in addition to being unacceptable due to the performance
degradation it causes (10 - 50 times increase in processing time).
The application is single threaded, there is only 1 persistence manager,
and there are no other transactions (or even connnections) to the database.
Relevant configuration info:
[Thread-20] kodo.jdbc.JDBC - Using dictionary class
"kodo.jdbc.sql.OracleDictionary" (Oracle Oracle9i Enterprise Edition
Release 9.2.0.5.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.5.0 - Production ,Oracle JDBC driver 9.0.1.0.0).
javax.jdo.option.ConnectionDriverName=oracle.jdbc.driver.OracleDriver
javax.jdo.PersistenceManagerFactoryClass=kodo.jdbc.runtime.JDBCPersistenceManagerFactory
javax.jdo.option.Multithreaded=false
javax.jdo.option.NontransactionalWrite=false
javax.jdo.option.NontransactionalRead=false
javax.jdo.option.RetainValues=false
javax.jdo.option.RestoreValues=false
kodo.ConnectionFactoryProperties=(MaxActive\=5)
kodo.jdbc.DBDictionary=oracle(StoreCharsAsNumbers\=false, BatchLimit\=0)
kodo.DataCache=true(CacheSize\=5000)
kodo.RemoteCommitProvider=sjvm
kodo.QueryCache=true(CacheSize\=1000)
It appears that it could be a problem with the state-image not recognizing
the difference between null and empty string, or an inconsistency in the
data cache.--
Marc Prud'hommeaux
SolarMetric Inc.