ObjectDB ObjectDB

Internal Website Search

21-30 of 198 resultsRefresh

Optimistic lock failed

: Failed to commit transaction: Optimistic lock failed for object com.example.MyEntity#3 (object ... you, Carl FastModel Ben Schreiber Hi, Locking in general is explained on: http://www.objectdb.com/java/jpa/persistence/lock If you must avoid optimistic lock exceptions you can use pessimistic exceptions

internal object DB locking in an embedded multi threaded application

locking. When profiling our app in JVisualVm we notice a large number of threads are blocked ... : BLOCKED at com.objectdb.o.MST.Vb(MST.java:1293) - waiting to lock <3a678c0> (a com ... .o.SFL.ah(SFL.java:998) - locked <67fc75bc> (a com.objectdb.o.LFL) at com.objectdb.o.MST.ah

Optimistic Locking

We are having problems with optimistic locking. I made a simple test case to try to induce an optimistic lock. I have two users logged on to our system. They both read and display the same data ... not get an optimistic lock exception, so the database has user 2’s change. Do you have a simple test

Undeployment of an remote Glassfish application locks objectdb log file

can delete the folder. The locked file problem does not exist if I deploy the WebApplication on an local Glassfish server. How can I undeploy the application without getting the logfile locked ... is the logfile at c:/ locked. The problem from the begining was that because glassfish could't undeploy

Optimistic locking failure

Optimistic locking failure: I am using a Semaphore to force this execution of concurrents ... . F. Martinez Please explain the test output: Sequential=true Lock=WRITE Thread[Thread-2,5,main ... =2 value=10, B2 version=2 value=30 Sequential=false Lock=WRITE Thread[Thread-6,5,main] READ  A1

EntityTransaction.commit() does not release a pessimistic lock

It appears that EntityTransaction.commit() does not release a pessimistic lock -> test code ... (); } } kurti Matt K. You are right. Pessimistic locks are not released automatically (by default ... values after commit and the application can still use them for further processing and update. Locks

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

Pessimistic lock timeout - blocks indefinitely

to update the object. I'm using a pessimistic lock with timeout as follows: Map<String,Object> properties = new HashMap<String,Object>(); properties.put("javax.persistence.lock.timeout", 5000 ... get released at the correct time but thrown a LockTimeoutException implying that the first lock wasn't


<LockModeType> Lock modes can be specified by means of passing a LockModeType argument to one of the javax.persistence.EntityManager methods that take locks ( lock, find, or refresh) or to the Query.setLockMode() or TypedQuery.setLockMode() method. Lock modes can be used to specify either optimistic or

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