Internal Website Search

database file is kept locked by the old Glassfish application (class loader) because of a missing ... ;(which should release the database file lock) by Glassfish. As a workaround - try using ... . The difference is that, the file is not locked, however the class loader exception still exists and I

;recording enabled="false" sync="false" path="." mode="write" />     <locking version

(BufferedInputStream.java:286) java.io.BufferedInputStream.read(BufferedInputStream.java:345) - locked ... .objectdb.jpa.JpaQuery.getResultList(JpaQuery.java:407) - locked com.objectdb.jdo.PMImpl@778f3a48

#the_locking_element">disabling optimistic locking exceptions. Added support

"/> <property name="javax.persistence.lock.timeout" value="2000"/> ... > 

Could you please clarify how we could avoid it? This has really locked our work for a couple of days.

500Mb ObjectDb database opening issue

database if its file is not locked by Glassfish. See the connection url section in the locked up, I know that is not a very useful diagnostic.  Anyway, I can currently

; <locking version-check="true" />            ... ;                 <locking

contexts in the same process that function as two separate processes)? ObjectDB locks the database file to avoid concurrent access by different processes, but the lock may not be effective

. Improved concurrency by using lock free Synchronization (issue #2327). Fixed a regression optimistic lock exception bug (due to fix of