About optimistic

issue

Error during closing an entity manager

Hello, can you explain the the following exception? Caused by: com.objectdb.o._PersistenceException: Failed to read the value of field field com.btc.ep.architecture.bl.internal.dmos.types.NormalizedAccessPathImpl.accessPathRoot using reflection at com.objectdb.o._PersistenceException.b(_PersistenceException.java:45) ~[na:na] at com.objectdb.o.JPE.g(JPE.java:145) ~[na:na] at com.objectdb.o.ERR.f(ERR.java:56) ~[na:na] at com.objectdb.o.OBC.onObjectDBError(OBC.java:1560) ~[na:na] at com.objectdb.o.OBM.close(OBM.java:212) ~[na:na] ... We tested also 2.7.1_03 and with this one we get an optimistic lock exception without enhancement. If we enhance all entities then ... changed the exception from the one in #3 above to an optimistic lock exception. More information and possibly a test case that ...

 
manual

Database Management Settings

Explains settings and performance tuning of the ObjectDB Java object database for JPA/JDO.... attribute of the <locking> element specifies if optimistic locking is enabled. Optimistic locking is completely automatic and enabled by default in ObjectDB, ...

 
issue

again merger missing logs + objectdb exception

we are facing similar problems as we had before, in the log we have a lot of entries merger ... missing + an objectdb exception. Some objects in the system behave strange. This is a part of the log: ... [2017-09-26 12:16:14 #1222 store] SectionClassifier: SectionClassifier{238146996->merger[3309]-missing:1} [2017-09-26 12:16:25 #1223 store] SectionClassifier: SectionClassifier{238146996->merger[3309]-missing:1} ... healthy). It shows that this happens when an optimistic lock exception is thrown during commit, and failed (locked) objects ... Which trace? The log just shows locations of optimistic lock exceptions, which should fail regardless of printing their ...

 
forum_thread

Failed to commit transaction: Attempt to commit a rollback only transaction

Anyone know what this means?? Suddenly cropped up.   Failed to commit transaction: Attempt to commit a rollback only transaction (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:271) at javax.jdo.Transaction$commit.call(Unknown Source) ... 04:25 note: optimistic locking is off edit ... update 1: problem persists if optimistic locking set to true in config file update 2: problem goes ...

 
forum_thread

Pessimistic lock

Dear Sir or Madam, In the past we used the default Options in the JDO 1.0. See below for reference: javax.jdo.option.Optimistic=false javax.jdo.option.NontransactionalRead=true javax.jdo.option.NontransactionalWrite=false javax.jdo.option.RetainValues=true javax.jdo.option.RestoreValues=false Now we use the following options in DB2: #1 2016-08-25 05:40 Dear Sir or Madam, In the past we used the default Options in the JDO 1.0. See below for reference: ...

 
api-jdo

flush()

Flushes all dirty, new, and deleted instances to the data store.(Method of javax.jdo.PersistenceManager)

 
api-jdo

refresh(pc)

Refresh the state of the instance from the data store.(Method of javax.jdo.PersistenceManager)

 
api-jdo

getDataStoreConnection()

If this method is called while a datastore transaction is active, the object returned will be enlisted in the current transaction.(Method of javax.jdo.PersistenceManager)

 
api-jdo

getConnectionFactory2()

Get the second data store connection factory.(Method of javax.jdo.PersistenceManagerFactory)

 
api-jdo

setConnectionFactory2Name(connectionFactoryName)

Set the name for the second data store connection factory.(Method of javax.jdo.PersistenceManagerFactory)