About pessimistic

41-50 of 52Refresh
Result
1

ObjectDB version 2.2.8

NullPointerException-s (issues #365, #366, #368). Fixed a pessimistic locking deadlock (issue #342).
Result
1

ObjectDB version 2.3.1

. Improved UnsupportedOperationException error message. Fixed a pessimistic lock timeout bug (issue #520
Result
1

ObjectDB version 2.3.2

of Long) and then updated. Fixed retrieval with pessimistic lock to bypass cache and to force refresh.
Result
1

ObjectDB version 2.6.8

Version 2.6.8 Added JPA XML validation schema files to Maven/JEE objectdb.jar. Added automatic release of pessimistic locks on client-server connection failure. Fixed an OptimisticLockException bug on commit after flushing a removed modified entity object. Fixed a NullPointerExeption on new index
Issue
1

InternalException during producer/consumer scenario

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

NPE at com.objectdb.jpa.JpaQuery.getResultList

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

ObjectDB 2 JDO Manual

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

Optimistic lock failed

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

Some technical questions

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

Threaded Test - Failed to commit transaction: Unexpected internal exception

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