ObjectDB Database Search

._OptimisticLockException: Optimistic lock failed for object model.UserSession#28 (object has version ... be wrong here. EDIT: Merge will attach Willks William Optimistic locking is enabled by ObjectDB automatically even if no version field is defined. You can disable optimistic locking checks  

Hi, ObjectDB looks interesting. Have two technical questions... (1) what locking model does ... you, Andrej andrej Andrej Gabara (1) what locking model does ObjectDB use? I.e. 2PL or MVCC? Do writers block readers? Do readers block writers? ObjectDB implements the standard JPA locking model

locking method that is used by ObjectDB 1.x. Try running ObjectDB in a process with no permission ... how to do this. And if write permission permission is blocked for the parent folder, won't ObjectDB locking method ... for the parent folder, won't ObjectDB locking method throw exceptions if it does not get the write permission

lock exception of the removed entity. If this operations on the entity are executed in only one plugin ... flushing changes to the database. You may also  disable optimistic locking checks   ... plugins. This leads to the optimistic lock exception. But the ObjectDB throws the changes of the entity

.java:176) com.objectdb.o.IXM.Yz(IXM.java:100) com.objectdb.o.MST.X(MST.java:1194) - locked com.objectdb.o.MST@1881a6d5 com.objectdb.o.MST.Z2(MST.java:1181) - locked com.objectdb.o.MST@1881a6d5 com.objectdb.o.IXA$1.run(IXA.java:418) - locked com.objectdb.o.LKM@7b5315ca

against the same objects being queried by the other client. Seems like some sort of locking problem ... locking is off dmoshal David Moshal update 1: problem persists if optimistic locking set to true in ... . It is possible that this is some sort of a locking issue. Notice that disabling version check

: The process cannot access the file because another process has locked part of the file Normally ... parents). ObjectDB provides some file locking protection, but unfortunately it is incomplete in ... /coreSystemDb__.7z?rlkey=63nr8o89wydf4klpg843a6rf9&dl=0 the problem with the locking arises if we just open

, to reduce the chance of an optimistic lock failure.             pm ... ;     // In case of an optimistic lock failure, get the latest version, and loop back to redo ... of an optimistic lock failure. Make changes and commit them. Handle

call to the PersistenceManagerFactory , locking down set/get methods of the Symbol class via java.util.concurrent. locks .ReentrantReadWriteLock locks , and varying the length (number of actions) within a transaction

the PersistenceManagerFactory as well to close the database file (and release the lock ) . support Support I ... the lock so that database files can be deleted     PersistenceManager pm = getPM ... do. May be, this thread is having the lock and that is the reason, we are unable to delete the odb file. I

database file is kept locked by the old Glassfish application (class loader) because of a missing invocation of EntityManagerFactory 's close  (which should release the database file lock ) by  ... still have the same problem. The difference is that, the file is not locked , however the class loader

.read(BufferedInputStream.java:345) - locked java.io.BufferedInputStream@294f1aa com.objectdb.o.NTS.n ... .objectdb.o.QRR.i(QRR.java:129) com.objectdb.jpa.JpaQuery.getResultList(JpaQuery.java:407) - locked com

locking (unless disabled in the configuration). You can use refresh  to get an up to date version ... ) you can use explicit locking . support Support That was not exactly what I meant: Take the following example

You should be able to drop the entire database if its file is not locked by Glassfish. See the connection ... for me, sometimes it does not, and I don't know why or under what circumstances, perhaps something gets locked

is locked for reading Try it a again also when the file is locked for reading/writing. These checks

) @GeneratedValue private Long id; /** * Version of object, supporting optimistic lock */ @Column (name = "opt_ lock ") @Version() private Long optimisticLock; /** * Flag to disable entity */ @Column private

Is it possible to change a LockTimeout for pessimistic  lock ? glaz Alexandr Kurucin Currently ObjectDB throws a LockTimeoutException immediately when a pessimistic lock cannot be granted. Future versions will support timeout setting. You may fill a feature request to increase the priority of this feature.   support Support

it is the other side of the first stack trace, which locks that monitor. support Support This is not related ... threads (e.g. database pages) is much more extensive so lock competition is more likely

to see a deadlock. The profiling info does not include lock and deadlock information.   support ... . Both threads require locks  on both the  EntityManager and the EntityManagerFactory but in

) and then it happens again that we run into a dead lock   Maybe the additional picures ... until its completion (e.g. by using join). support Support We run still into a dead lock . I adding

: "Attempt to lock a non entity object". The change stays on the screen, but is not persisted

to minimize the time that the database is locked for backup (e.g. when the connection between the client

Is there a way to setup a database file that will be accessed in embedded mode, such that it is locked with a password.  Thereby making it impossible to use ObjectDB to access the contents of the file without providing the correct password when obtaining a connection.  In my case, I'm

of the file? support Support I think not, since the file once writen/created would be locked

 as a lock object. In your test case you only have one EntityManagerFactory , right

(included in the download). Added support of disabling optimistic locking exceptions . Added support

, or if ObjectDB is doing some sort of queue/ locking  whose depth is determined by this setting

folder, however I've got a few questions I couldn't find answers for: How will locking take place

MBs). support Support Thanks. It solved the dead lock . edy_at_ssn Edy Oey

based databases (in server mode the database is locked so drop can't be used). The only method I've

) "The process cannot access the file because another process has locked a portion of the file" shows ... then the locker is another process, i.e. this is not a lock by your application process ... ObjectDB locks the database file when it is in use so accessing the database with the Explorer

that this happens when an optimistic lock exception is thrown during commit, and failed ( locked ... hgzwicker Hans-Georg Zwicker Which trace? The log just shows locations of optimistic lock exceptions ... when there is an optimistic lock exception on a large object (= ~2KB). Assuming you have ObjectDB 2.7.2

.lang.InterruptedException at java.util.concurrent. locks .AbstractQueuedSynchronizer ... after that commit might succeed in locking an object that was locked by the committed transaction. Passing null

(entity version = 1) and committed, during the commit an optimistic lock exception is thrown. The version ... : Failed to commit transaction: Optimistic lock failed for object com.btc.ep.base.bl.internal.entities ... : com.objectdb.o._OptimisticLockException: Optimistic lock failed for object com.btc.ep.base.bl

Added support of JPA UPDATE and DELETE queries ( issue #12 ). Added support of pessimistic lock timeout ( javax.persistence. lock .timeout ). Added implementation of the getParameters method. Added exception on pessimistic locking retrieval with no active transaction. Improved support of entity

) - waiting to lock (a com.objectdb.o.TYM) at com.objectdb.o.TYM.y(TYM.java:791) at com.objectdb.o.MST.ac(MST.java:956) at com.objectdb.o.MST.aj(MST.java:927) - locked (a com.objectdb.o.MST) at com ... ) at com.objectdb.jpa.EMImpl.find(EMImpl.java:604) - locked (a com.objectdb.jdo.PMImpl) at com.objectdb

also 2.7.1_03 and with this one we get an optimistic lock exception without enhancement. If we enhance ... ;an optimistic lock exception. More information and possibly a test case that demonstrates the exception ... of the optimistic lock exception and we fixed it in our code. From my sight of view this issue is fixed. btc_es BTC EmbeddedSystems

two processes. ObjectDB protects against this option by using a file lock (e.g. you probably see an error ... this Java file lock is system dependent and might not work in some systems (e.g. if the file

two separate processes)? ObjectDB locks the database file to avoid concurrent access by different processes, but the lock may not be effective on some systems, or in the same process

lock free Synchronization ( issue #2327 ). Fixed a regression optimistic lock exception bug

however, married to JDO, although I think it's good. Its lack of true (before commit) pessimistic locking ... small for most users, and in some of them JPA is better (e.g. in locking , as you noted). I think

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 building

Hello, I'm using the Java Persistence API (JPA) in a library to not lock myself in to using a specific database. In a project that uses said library, I'm using ObjectDB because it is fast and eliminates the need for another dependency to an ORM, such as Hibernate, since it implements the JPA

Attempt to solve temporary files locking issues on Linux.

of connections specified in configuration. Fixed optimistic lock exception on removing of a flushed modified

( issue #2794 ). Fixed an enum optimization regression ( issue #2794 ). Fixed a temporary files locking issue on Linux ( issue #2794 ).

O'Hare It seems as a separate issue. Maybe related to pessimistic locking . Can you provide a test

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

UnsupportedOperationException  error message. Fixed a pessimistic lock timeout bug ( issue #520 ). Fixed

that is somehow locked . Closing the entitiy manager should free the memory - but freeing no longer objects