Fast Object Database for Java - with JPA/JDO support

Internal Website Search

11-20 of 90 resultsRefresh

Optimistic lock failed

: Failed to commit transaction: Optimistic lock failed for object com.example.MyEntity#3 (object ... /jpa/persistence/lock If you must avoid optimistic lock exceptions you can use pessimistic exceptions, but it is more efficient to remain with optimistic locking (which is the default) and just handle

Optimistic locking failure

Optimistic locking failure: I am using a Semaphore to force this execution of concurrents ... . Martinez You are right again. To support this, starting build 2.3.7_24 OPTIMISTIC (READ) is implemented as OPTIMISTIC_FORCE_INCREMENT (WRITE). This is allowed by JPA, and is required by ObjectDB in order

Optimistic lock failed for object

Hi, 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 ... is for optimistic locking. My question was about pessimistic locking (specifically, pessimistic write

Optimistic lock failed : object has version .. instead of ..

.OptimisticLockException Optimistic lock failed for object entities.Record#'1405/838/2011/121' (object ... :381) ... Thank you! adibe Adi Be Optimistic locking is explained in this manual page. support Support

Remove a modified entity cause an optimistic lock exception

. The second example is an OSGi program which fails with an optimistic lock exception. Both examples ... ). Can you explain the optimistic lock exception? It seems that the first level cache contains yet a dirty entity

Optimistic lock

Hello When I get an optimistic lock on an object, refresh(), start trans and persist? Will the changes made to the object before the violation be retained or must they be duplicated in the retry code? Assuming it affects only one object. tia. cpanon CP The exact situation

Optimistic locking: prevent version increment on entity collection attribute

Hello, I have an entity E with an attribute which is a collection of entities (one to many relationship) with an optimistic locking strategy supported by a version field. Is it possible to prevent the increment of the version of entity E when entities are added to or removed from the collection

Optimistic Lock Exception With No Concurrency

Optimistic Lock Exception With No Concurrency


.setLockMode() or TypedQuery.setLockMode() method. Lock modes can be used to specify either optimistic or pessimistic locks. Optimistic locks are specified using LockModeType.OPTIMISTIC and LockModeType.OPTIMISTIC_FORCE_INCREMENT. The lock mode type values LockModeType.READ and LockModeType.WRITE

ObjectDB Object Database Features

(can be injected to a @Version field). Optimistic locking (always active). Implicit pessimistic ... , OPTIMISTIC/PESSIMISTIC. Database Tools and Utilities ObjectDB provides the following database tools

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support