16 | Degrading performance overtime to see considerable degrade in performance caused internal objectdb locking: "pdncrttorfo42-WSAgent-1 ... ) - waiting to lock <64c56ec3> (a com.objectdb.o.PGC) owned by "ODB-FileWriter" t@116 at com ... .ah(SFL.java:998) - locked <75608da2> (a com.objectdb.o.LFL) at com.objectdb.o.MST.ah(MST.java:1746 |
3 | javax.persistence.PessimisticLockException Interfaces: Serializable Thrown by the persistence provider when an pessimistic locking conflict occurs |
3 | LockModeType.OPTIMISTIC_FORCE_INCREMENTEnum Constant javax.persistence.LockModeType OPTIMISTIC_FORCE_INCREMENT Optimistic lock, with version update. Since: JPA 2.0 |
3 | LockModeType.OPTIMISTICEnum Constant javax.persistence.LockModeType OPTIMISTIC Optimistic lock. Since: JPA 2.0 |
3 | setHint(hintName, value) timeout hint. Depending on the database in use and the locking mechanisms used by the provider, this hint |
3 | LockModeType.NONEEnum Constant javax.persistence.LockModeType NONE No lock. Since: JPA 2.0 |
3 | setHint(hintName, value) on the standard timeout hint. Depending on the database in use and the locking mechanisms used by |
3 | NamedQuery.lockModeAnnotation Element javax.persistence.NamedQuery LockModeType lockMode (Optional) The lock mode type to use in query execution. If a lockMode other than LockModeType.NONE is specified, the query must be executed in a transaction. Default value: javax.persistence.LockModeType.NONE Since: JPA 2.0 |
3 | Query fails with failed to read has locked a portion of the file" shows some results that may be relevant, for example: https ... -cannot-access-the-file-because-another-process-has-locked-a-portion-of-the-file-57?forum=visualstudiogeneral If the answer on that thread is correct then the locker is another process, i.e. this is not a lock |
0 | getOptimistic()Method javax.jdo.Transaction boolean getOptimistic() Optimistic transactions do not hold data store locks until commit time. Returns: the value of the Optimistic property. Since: JDO 1.0 |
