Home » Search

About lock

101-110 of 161Refresh
Issue
1

ObjectDB 2 JDO Manual

commit) pessimistic locking is something I miss, for example, and it to some degree it is a compromise ... , and in some of them JPA is better (e.g. in locking, as you noted). I think you need really good reasons
Forum
1

ODB IndexActivation NullPointerException

:  Sometimes we get still the Nullpointer (IXM.java:322) and then it happens again that we run into a dead lock   Maybe ... (e.g. by using join). We run still into a dead lock. I adding a few screenshots and I hope it help
Forum
1

Replication issue, Replayer failing due to NullPointerException.

="512mb" /> <locking version ... " /> <locking version-check="true" />
Forum
1

Transaction isolation support?

of that specific object using the first EntityManager, due the default optimistic locking (unless disabled in ... the same object by different users concurrently (even for read) you can use explicit locking
Issue
1

Unexpected error when loading all entity instance

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 on some systems, or in the same
Result
1

ObjectDB version 2.1.0

Version 2.1.0 Added Online Backup utility (issue #16). Added Master-Slave Replication / Clustering (issue #17). Added a PDF version of the ObjectDB manual (included in the download). Added sample (tutorials) Maven projects (included in the download). Added support of disabling optimistic locking
Result
1

ObjectDB version 2.2.1

Version 2.2.1 Added support for using ObjectDB with JBoss AS 6.0 / 6.1. Fixed several bugs in handling eager fetch. Fixed a pessimistic locking bug. Fixed a bug in using primary key fields in queries. Fixed a bug in queries on deleted objects before commit / flush.
Result
1

ObjectDB version 2.2.8

NullPointerException-s (issues #365, #366, #368). Fixed a pessimistic locking deadlock (issue #342).
Result
1

ObjectDB version 2.2.9

lock problem. Fixed a bug in managing a new entity after an attempt to find it in the database. Fixed
Result
1

ObjectDB version 2.3.1

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