5 | unable to update table in slave server database" path="." mode="write" /> <locking version-check="true" /> <processing cache="64mb" max-threads="10 |
5 | significant performance decrease="write" /> <locking version-check="true" /> <processing cache="2048mb" max-threads="10 |
5 | Activation Issue="write" /> <locking version-check="true" /> <processing cache="64mb" max-threads="10 |
5 | Explorer in 2.3 to lock a non entity object". The change stays on the screen, but is not persisted to the database |
5 | Memory Leak in EntityManagerFactory ? using the relevant EntityManagerFactory as a lock object. In your test case |
5 | Understanding Database max-threads objectdb.conf Settings Option is doing some sort of queue/locking whose depth is determined by this setting (and entries |
5 | WORM (Write once read many) support of the file? support Support I think not, since the file once writen/created would be locked |
1 | Exception occurs on Linux during commit.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java |
1 | Use temporary files to enable very large transactions="false" sync="false" path="." mode="write" /> <locking version-check="true |
1 | ObjectDB 2.8.5Fixed a bug in using AS in SELECT NEW (breaks some Spring Data JPA queries). Fixed a bug in tracking changes to new collections after flush (issue #2640). Fixed a StackOverflowError on no access permission to objectdb.conf (issue #2643). Fixed a bug in managing pessimistic locks after using |
