Internal Website Search
11-20 of 200 resultsRefreshLock prevents PersistenceManager.close when retainValues = false shows this is the result of a lock) when I try to close the persistence manager ... .read(BufferedInputStream.java:265) - locked <15cdd45> (a java.io.BufferedInputStream ... ) at java.lang.Thread.run(Thread.java:748) Locked ownable synchronizers | |
Pessimistic Lock Timeouts setting way for Lock Timeouts. However, there is a standardised query 'hint' that can be setup to make the underlying DB lock a record for a specific time. The hint property is: "javax.persistence.lock ... is that once the pessimistic lock is in place on the record, a subsequent access (which is a valid scenario | |
locks on pure query activities of our threads that are just doing simple queries (just selects, no update or delete ...) show locks like these (question is: why there are locks and how could we get rid of that): lock < | |
Pessimestic Locking doesn't release when application unexpectedly terminates. a cluster singleton. Our approach to this was to use Objectdb's pessimestic locking. This seems to work, but if the owner of the current pessimestic lock abruptly quits without releasing the lock ... that a client (lock owner is no longer connected) and therefore release the lock ? | |
"Attempt to lock a non entity object" error produces the error "Attempt to lock a non entity object" session.rollback ... () { try { session.beginTransaction(); session.lock ... ------------------------------------------------------------- Attempt to lock a non entity object | |
Where Does ObjectDB Block/Lock?> Questions about blocking/locking. With my PersistenceManager multiThreaded=true architecture, I desire to know where ObjectDB is actually blocking/locking so I might adapt to achieve better concurrency. 1) Where are locks when accessing PersistenceManager by multiple threads | |
Optimistic lock failed for object Hi, I seem to be getting a lot of these optimistic locking errors: Caused by: com.objectdb.o._OptimisticLockException: Optimistic lock failed for object Is there any way to force the database to use pessimistic locking only? I've | |
EntityManagerFactory objects being locked during EntityManager creation with ObjectDB wherein the EntityManagerFactory objects are being locked during EntityManager object ... ="background-color:#f1c40f;">waiting to lock <76bf096d> ( - locked <19e9ce09> (a java | |
JPA Entity Fields conjunction with lock">optimistic locking (as explained in the lock">Locking in JPA section in chapter 3). You can expose entity ... . Therefore, optimistic locking is supported by ObjectDB even when a version field is not defined | |
each 1-2 days objects on some objectdb level lock/block each other thread dump shows a page cache lock (0x00000000b6681e10) by one thread. The second thread dump ... but a very short lock that is not expected to cause issues. The change in ObjectDB version doesn't ... ; <locking version-check="true" /> <processing cache="4096mb" max-threads="80 |