5 | ODB-WeakRefPurger threads not closing at all State: WAITING on java.lang.ref.ReferenceQueue$Lock@6069d1ca Total blocked: 0 Total waited: 1 |
5 | Performance tuning, best practices="false" sync="false" path="." mode="write" /> <locking version-check="true" /> <processing cache |
5 | Unable to execute update query after the error occoured: 0 lock.lck 4,0K pages0.dat 3,8G UpdateQuery_4398.mrg 3,8G insgesamt |
5 | Weird behaviour with enhanced classes and embedded entities() to the proxied list (I am pretty sure I do the locking/synchronizing the right way |
5 | Drop the entire database, Change the schema technique already, but it means I have to stop the container to be sure the DB file is not locked - I |
5 | how to operate with same object but two different Thread on database. and threads. Locks are used to avoid conflict in updating the same object as the same time. support Support |
5 | exception during online backup cannot access the file because another process has locked a portion of the file at java.io |
5 | Connection is closed Caused by: java.io.EOFException="false" sync="false" path="." mode="write" /> <locking version-check="true" /> <processing |
1 | NPE at com.objectdb.jpa.JpaQuery.getResultList(); } } longpat Brian O'Hare It seems as a separate issue. Maybe related to pessimistic locking |
1 | ObjectDB 2.2.8 (issues #365, #366, #368). Fixed a pessimistic locking deadlock (issue #342). |
