About lock

71-80 of 178Refresh
Forum
4

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
JDO Doc
4

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
JPA Doc
4

javax.persistence.LockTimeoutException

: Serializable Thrown by the persistence provider when an pessimistic locking conflict occurs that does
JPA Doc
4

LockModeType.NONE

Enum Constant javax.persistence.LockModeType NONE No lock. Since: JPA 2.0
JPA Doc
4

LockModeType.OPTIMISTIC

Enum Constant javax.persistence.LockModeType OPTIMISTIC Optimistic lock. Since: JPA 2.0
JPA Doc
4

LockModeType.OPTIMISTIC_FORCE_INCREMENT

Enum Constant javax.persistence.LockModeType OPTIMISTIC_FORCE_INCREMENT Optimistic lock, with version update. Since: JPA 2.0
JPA Doc
4

LockModeType.PESSIMISTIC_FORCE_INCREMENT

Enum Constant javax.persistence.LockModeType PESSIMISTIC_FORCE_INCREMENT Pessimistic write lock, with version update. Since: JPA 2.0
JPA Doc
4

LockModeType.PESSIMISTIC_READ

Enum Constant javax.persistence.LockModeType PESSIMISTIC_READ Pessimistic read lock. Since: JPA 2.0
JPA Doc
4

LockModeType.PESSIMISTIC_WRITE

Enum Constant javax.persistence.LockModeType PESSIMISTIC_WRITE Pessimistic write lock. Since: JPA 2.0
JPA Doc
4

NamedQuery.lockMode

Annotation 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