About PESSIMISTIC_READ

191-200 of 200Refresh
Forum
0

zip file or JAR manifest missing

/objectdb.jar Some of projects can read the DB, but others can not read or write the DB. Exception in ... .getEntityManager(); public void read(){   int iCnt = 10;   while (--iCnt>=0){    trans.begin();    Page ... ");   SingleManager.clearDB("URI");   new PageTest().read(); } } the version 2.2.8_6 can not pass, saying "use
Result
0

ObjectDB version 2.2.1

Version 2.2.1 Added support for using ObjectDB with JBoss AS 6.0 / 6.1. Fixed several bugs in handling eager fetch. Fixed a pessimistic locking bug. Fixed a bug in using primary key fields in queries. Fixed a bug in queries on deleted objects before commit / flush.
Result
0

ObjectDB version 2.2.8

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

ObjectDB version 2.3.1

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

ObjectDB version 2.3.2

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

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
0

InternalException during producer/consumer scenario

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

NPE at com.objectdb.jpa.JpaQuery.getResultList

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

Optimistic lock failed

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

Some technical questions

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