Home » Search

About lock

71-80 of 161Refresh
JPA Doc
3

LockModeType.PESSIMISTIC_FORCE_INCREMENT

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

LockModeType.PESSIMISTIC_READ

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

LockModeType.PESSIMISTIC_WRITE

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

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

setHint(hintName, value)

timeout hint. Depending on the database in use and the locking mechanisms used by the provider
JPA Doc
3

setHint(hintName, value)

on the standard timeout hint. Depending on the database in use and the locking mechanisms used by
JDO Doc
3

setOptimistic(optimistic)

Method javax.jdo.Transaction void setOptimistic(   boolean optimistic ) Optimistic transactions do not hold data store locks until commit time. If an implementation does not support this option, a JDOUnsupportedOptionException is thrown. Parameters: optimistic - the value of the Optimistic flag. Since: JDO 1.0
Forum
3

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
Forum
3

Several parallel threads to speed up query on one DB

used to do a clear after running each query - The lock contention disappears when I removed the "em ... (timeline) and the lock contention view. You can see that Thread R1 is running smoothly with no lock ... - and they seem to get to lock each other many times for small amount time. Thanks Thank you for the test case. Some locking
Forum
3

How to do multithreading with embedded ObjectDB

, rather than concurrently:     synchronized (lock) {         em.createQuery("UPDATE Point SET x = x + 1").executeUpdate();     } Your lock object must be one object that is shared by all the threads. 2. Use ObjectDB / JPA locking, by setting a pessimistic locking timeout, e.g. by: Map