Home » Search

About commit

21-30 of 200Refresh
Forum
19

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
Issue
19

ObjectDB-2.6.9: Failed to commit transaction: Failed to set numeric value of field property Element.id using reflection

The following error is reported for objectdb-2.6.9.jar: Failed to commit transaction: Failed ... .persist(project); //rely on Cascade all on ownedElements. em.getTransaction().commit ... .6.9] javax.persistence.RollbackException Failed to commit transaction: Failed to set numeric value
Issue
19

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: commit="true
Forum
19

Access entity version before commit transaction

commiting the transaction: 1. Change entity field e.g. from a to b 2. Create a change entry in database ... the transaction before commiting it. How can I achieve this? If I add something to a collection field ... : transactional.execute() just creates a transaction (entityManager.getTransaction().begin();) and commits
Issue
19

Error in production. Failed to commit transaction: Unexpected database state: BTree -152 is not found

.Read .doGet (115 ): Failed to commit transaction: Unexpected database state: BTree -152 is not found [ObjectDB 2.5.5] javax.persistence.RollbackException Failed to commit transaction: Unexpected database state: BTree -152 is not found (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:302
Issue
19

Exception occurs on Linux during commit

(under tomcat) I get the following exception during a call to commit. Code: pm.currentTransaction().begin(); pm.makePersistent(p); pm.currentTransaction().commit();   Stacktrace: [ObjectDB 2.4.0] Unexpected ... .EMImpl.commit(EMImpl.java:276) at com.golocal.places.PlacesProvider.addPlaceToSearch
Issue
19

Threaded Test - Failed to commit transaction: Unexpected internal exception

run the example code with fewer consumer (I just tried 2) it seems to just hang on the "take" commit ... ();             try {                 em.persist(p);                 em.getTransaction().commit ... );                 em.getTransaction().commit();                 System.out.println("take " + p
Manual
18

Locking in JPA

separately. Optimistic locking is applied on transaction commit. Any database object ... is being performed on an old version of a database object, for which another update has already been committed ... must be revealed earlier (before transaction commit) pessimistic locking can be used. When using
Manual
18

Setting and Tuning of JPA Queries

em can be visible to anyone who uses em, even before committing the transaction (but not to users ... , which has two values: AUTO - changes are flushed before query execution and on commit/flush. COMMIT - changes are flushed only on explicit commit/flush. In most JPA implementations the default is AUTO. In
Forum
18

com.objectdb.o._RollbackException: Failed to commit transaction

Check the Exception below: (occurs sometimes, ObjectDB 2.3.6_14) com.objectdb.o._RollbackException: Failed to commit transaction: at com.objectdb.o.JPE.g(JPE.java:89) ~[JPE.class:na ... .onObjectDBError(OBC.java:1493) ~[OBC.class:na] at com.objectdb.jpa.EMImpl.commit(EMImpl.java:279