ObjectDB ObjectDB

Internal Website Search

11-20 of 200 resultsRefresh

Rollback after commit fail

() persist object1 em.getTransaction().commit(); } catch(...){ em.getTransaction ... ().commit(); } catch(...){ em.getTransaction().rollback(); } Parallel running threads caused that second thread commit will fail (primary key reuse exception), the exception is caught

EntityTransaction.commit() does not release a pessimistic lock

It appears that EntityTransaction.commit() does not release a pessimistic lock -> test code ... .getTransaction().begin(); em.persist(new Account(0)); em.getTransaction().commit ... ); em1.getTransaction().commit(); System.out.println(em1.getLockMode(a1)); // -> PESSIMISTIC_WRITE

Memory Leaks after COMMIT operation (checked on versions 2.6.5 & 2.6.6.b01)

.COMMIT ); if ( m_EntityManager.isOpen() ) { m_EntityManager.getTransaction().begin ... ); } m_EntityManager.getTransaction().commit(); m_EntityManager.flush(); m ... .commit

Is it possible to commit only specific elements?

Hello, As stated above, I would like to know if it is possible to commit only specific elements, or ... , retrieving only the needed ones, creating new ones (which I want to commit), detaching the ones I've previously retrieved and finally committing. My context is big data and performance is an issue. btc

Populating entity id before transaction commit

Hi, I have a question about populating auto generated id before transaction commit. We are using ... transaction is committed so all returned entities are not populated with ID in this context. How can I force ODB to populate entity ID before transaction is committed? Or maybe there is another way

Storing JPA Entity Objects

.getTransaction().commit(); The Employee instance is constructed as an ordinary Java object and its initial ... is committed. An IllegalArgumentException is thrown by persist if the argument is not an instance ... managed by the EntityManager) or by commit. Referenced Embedded Objects The following code stores

NullpointerException when execute a commit

to commit transaction: Unexpected internal exception at com.objectdb.o.MSG.d(MSG.java:75) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:304) .... Caused by: com.objectdb.o.InternalException: Unexpected ... .EMImpl.commit(EMImpl.java:299) ... 45 more Caused by: java.lang.NullPointerException at com.objectdb.o

Unexpected Exception during commit

.9_01] javax.persistence.RollbackException Failed to commit transaction: Unexpected internal exception (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:277) at com ... .commit(EMImpl.java:274) ... 15 more Caused by: java.lang.NullPointerException

Sometimes cascade persist does not work during commit

A, afterwards not persisted entities B are added to entity A. At the end a commit is executed and the commit persists the entities B automatically by cascading. But sometimes the cascading doesn't ... ? // persist configuration: <cascade-persist always="auto" on-persist="true" on-commit="true" /> public

Unexpected not reproducable exception during commit

._RollbackException: Failed to commit transaction: 2019-02-07 04:22:53 - [main] ERROR com.btc.ep.base.dal ... .btc.ep.base.dal.MigrationUtility - PROFILE MIGRATION: at com.objectdb.jpa.EMImpl.commit(EMImpl ... .btc.ep.base.dal.MigrationUtility - PROFILE MIGRATION: at com.objectdb.jpa.EMImpl.commit(EMImpl

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