125 | Lock prevents PersistenceManager.close when retainValues = false this is the result of a lock) when I try to close the persistence manager, but only if 'retainValues' is set ... .BufferedInputStream.read(BufferedInputStream.java:265) - locked <15cdd45> (a java.io ... .java:624) at java.lang.Thread.run(Thread.java:748) Locked ownable synchronizers |
124 | Pessimistic Lock Timeouts settingHi, I realise that JPA2 doesn't necessarily define a standard API 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.timeout" I have a situation |
123 | locks on pure query activities 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): log1: "qtp1523553211-271" #271 prio=5 ... ) - waiting to lock <0x0000000202239c10> (a com.objectdb.o.LFL) at com.objectdb.o.PAG.au |
119 | Pessimestic Locking doesn't release when application unexpectedly terminates.. 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 it doesn't get released. Is there anyway the server can detect that a client (lock owner is no longer connected |
114 | Where Does ObjectDB Block/Lock? titled, "Sample JDO Architecture for Follow Up Questions". Questions about blocking/locking ... blocking/locking so I might adapt to achieve better concurrency. 1) Where are locks when accessing PersistenceManager by multiple threads? 2) Does it lock at PersistenceManager.currentTransaction()? 3 |
114 | "Attempt to lock a non entity object" error and then doCancelEdit works fine. Second time I doEdit produces the error "Attempt to lock a non entity ... () { try { session.beginTransaction(); session.lock(subjectJList.getSelectedValue ... ------------------------------------------------------------- Attempt to lock a non entity object |
112 | Optimistic lock failed for objectHi, 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 tried various xml configurations, and also various transaction |
27 | ObjectDB Object Database Features. Locking Automatic object versioning (can be injected to a @Version field). Optimistic locking (always active). Implicit pessimistic locking (JDO). Explicit pessimistic locking (JPA 2). Always Object Level locking. Lock modes: READ/WRITE, OPTIMISTIC/PESSIMISTIC. Database Tools and Utilities ObjectDB |
27 | Database Management Settings="." mode="write" /> <locking version-check="true" /> <processing cache="64mb" max-threads="10 ... operation is slower and the recording files are much larger when "all" is used. The <locking> element <locking version-check="true" /> The version-check attribute of the <locking> element specifies |
23 | each 1-2 days objects on some objectdb level lock/block each other The two thread dumps show two different waiting situations. The first thread dump shows a page cache lock ... it is not a deadlock but a very short lock that is not expected to cause issues. The change in ObjectDB ... enabled="false" sync="false" path="." mode="write" /> <locking version-check="true |
