About pessimistic

41-50 of 54Refresh
Result
3

ObjectDB version 2.2.4

Added support of JPA UPDATE and DELETE queries (issue #12). Added support of pessimistic lock timeout (javax.persistence.lock.timeout). Added implementation of the getParameters method. Added exception on pessimistic locking retrieval with no active transaction. Improved support of entity objects
Issue
2

InternalException during producer/consumer scenario

and LockMode set to PESSIMISTIC_WRITE. This results in the exceptions below. Could you advise on the errors
Issue
2

NPE at com.objectdb.jpa.JpaQuery.getResultList

(); } } It seems as a separate issue. Maybe related to pessimistic locking
Issue
2

ObjectDB 2 JDO Manual

commit) pessimistic locking is something I miss, for example, and it to some degree it is a compromise
Forum
2

Optimistic lock failed

If you must avoid optimistic lock exceptions you can use pessimistic exceptions
Forum
2

Some technical questions

fetch this object without blocking? Yes, if it has not been locked with pessimistic WRITE
Issue
2

Threaded Test - Failed to commit transaction: Unexpected internal exception

(                     LockModeType.PESSIMISTIC_WRITE).getSingleResult();                 em.remove(p
Forum
2

Where Does ObjectDB Block/Lock?

instances. In ObjectDB 1.x pessimistic locks were more efficient, but with ObjectDB 2.x optimistic locks
Result
2

ObjectDB version 2.2.8

(issues #365, #366, #368). Fixed a pessimistic locking deadlock (issue #342).
Result
2

ObjectDB version 2.3.2

) and then updated. Fixed retrieval with pessimistic lock to bypass cache and to force refresh.