Internal Website Search
11-20 of 200 resultsRefreshRollback after commit fail.createEntityManager(); em.getTransaction.begin() persist object1 em.getTransaction().commit ... .getTransaction.begin() persist object2 persist object1 em.getTransaction().commit ... threads caused that second thread commit will fail (primary key reuse exception), the exception is caught | |
EntityTransaction.commit() does not release a pessimistic lockIt appears that EntityTransaction.commit() does not release a pessimistic lock -> test code ... .getTransaction().commit(); // update EntityManager em1 = emf.createEntityManager ... _WRITE); a1.credit(10); em1.getTransaction().commit(); System.out.println(em1 | |
Memory Leaks after COMMIT operation (checked on versions 2.6.5 & 2.6.6.b01).setFlushMode( FlushModeType.COMMIT ); if ( m_EntityManager.isOpen() ) { m_EntityManager ... _EntityManager.persist( dataKey ); } m_EntityManager.getTransaction().commit(); m ... ; | | | | +---com.objectdb.jpa.EMImpl.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 ... my persistency context, 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 | |
CRUD Database Operations with JPA/EntityTransaction/commit">commit(); Operations that modify the content of the database ... are physically stored in the database only when the transaction is committed. The getTransaction().commit">commit(); In | |
NullpointerException when execute a commit.UserException: Failed 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 ... .EMImpl.commit(EMImpl.java:299) ... 45 more Caused by: java.lang.NullPointerException | |
Updating JPA Entity Objects/EntityTransaction/commit">commit(); The entity object is physically updated in the database when the transaction is committed. If the transaction is rolled back and not committed the update is discarded. On commit the persist operation can be cascaded from all the entity objects | |
Unexpected Exception during commit Failed to commit transaction: Unexpected internal exception (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:277) at com.fastmodel.fastplan.db.EntityManagerFactory.doFilter ... .bE(OBM.java:715) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:274) ... 15 | |
Sometimes cascade persist does not work during commit an entity 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 ... always="auto" on-persist="true" on-commit="true" /> public class CascadePersistDoesNotWork | |
[ODB1] Chapter 5 - JDO Connections here. pm.currentTransaction().commit(); } finally { if (pm.currentTransaction().isActive ... >commit() or rollback(). All the operations on the database ... are discarded. On the other hand, ending the transaction with commit() propagates |