103 | 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 |
102 | Failed to commit transaction: Attempt to reuse an existing primary key value (613).RollbackException Failed to commit transaction: Attempt to reuse an existing primary key value (domain.Pronostikoa:72) (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:289) at test.dataAccess ... , and at the commit clause it throws the exception. If you could explain to me why is it happening i |
101 | com.objectdb.o._RollbackException: Failed to commit transactionCheck 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 |
101 | finding post-persist pre-commit objectsHi, I'm wondering if there is a way to have post-persisted, pre-committed, objects show up in queries? ie: the object has been persisted, but not yet committed. Dave dmoshal David Moshal Yes, by setting the flush mode. support Support thanks, worked for me. dmoshal David Moshal |
101 | Query problem after transaction commit.begin ... persist(p) .. commit of a new object, my client program can no longer retrieve the old ... issue with a simple solution (e.g. changing flush mode from commit to auto could solve |
101 | NegativeArraySizeException on commiting a transactionHi, we started to get a java.lang.NegativeArraySizeException from ObjectDB upon changing an object in the DB and committing the transaction. I tried to repair the DB file with Database Doctor ... (and commit) after emptying its string fields? support Support If you use a deep nested embedded objects in |
20 | ObjectDB-2.6.9: Failed to commit transaction: Failed to set numeric value of field property Element.id using reflectionThe 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 ... .9] javax.persistence.RollbackException Failed to commit transaction: Failed to set numeric value |
20 | 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 |
20 | Threaded Test - Failed to commit transaction: Unexpected internal exception) it seems to just hang on the "take" commit. I've attached the objectdb log from these runs if that helps ... .persist(p); em.getTransaction().commit(); } catch(Exception e ... ).getSingleResult(); em.remove(p); em.getTransaction().commit |
20 | 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 |
