Fast Object Database for Java - with JPA/JDO support

Internal Website Search

31-40 of 56 resultsRefresh


the object just after the refresh. In that case - use pessimistic locks. support Support I read this before ... after the refresh. In that case - use pessimistic locks" However, my application runs a time critical ... me. Pessimistic locks might not help either, given #3 above, ie: it seems like last update wins, and changes


Enum Constant javax.persistence.PessimisticLockScope NORMAL This value defines the default behavior for pessimistic locking. The persistence provider must lock the database row(s) that correspond to the non-collection-valued persistent state of that instance. If a joined inheritance strategy


Interfaces: Serializable Thrown by the persistence provider when an pessimistic locking conflict occurs


with pessimistic locking is used and the entity no longer exists in the database. The current transaction


: Serializable Thrown by the persistence provider when an pessimistic locking conflict occurs that does

Optimistic lock failed for object

pessimistic locking only? I've tried various xml configurations, and also various transaction ... is for optimistic locking. My question was about pessimistic locking (specifically, pessimistic write locking). Your documentation seems unclear about that. dmoshal David Moshal Pessimistic locking is not

Pessimestic Locking doesn't release when application unexpectedly terminates.

(which is currently not implemented) is to use pessimistic locking with expiration time. For example ... as the connection is broken. support Support Hi Since I want to use Pessimistic Lock as a way of enforcing a cluster wide singleton of services, a pessimistic lock will potentially last forever or


. Also have the Explorer open Questions: a) what is it about? b) is there a setting for pessimistic mode? In my app, I ... more. I ran into the same error from a pessimistically locked entity (global tracking id generator ... the insertion test case. 5 threads/100 repetitions gave Optimistic lock error on pessimistically tracked

"Attempt to lock a non entity object" error

(),       LockModeType.PESSIMISTIC_WRITE); . . } //doEdit ... );         em.lock(p, LockModeType.PESSIMISTIC_WRITE);         System.out.println("After find and first lock ... ();         // next line throws IllegalArgumentException         em.lock(p, LockModeType.PESSIMISTIC_WRITE

How to do multithreading with embedded ObjectDB

. Use ObjectDB / JPA locking, by setting a pessimistic locking timeout, e.g. by: MapPESSIMISTIC_WRITE);         point.setX(point.getX() + 1); support Support

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