Home » Search

About commit

121-130 of 200Refresh
Forum
2

Soft Reference Object Cache Recommendation

(until commit). Your test (at #9 above) does not show strong references from ObjectDB to your Data instances after committing a transaction. Note that we got much smaller heap size (4MB) than reported by ... heap dump after commit, clicking right and selecting "Show nearest GC root" results with a VisualVM
JDO Doc
2

supportedOptions()

-uncommitted javax.jdo.option.TransactionIsolationLevel.read-committed javax.jdo.option
Forum
2

calling persist on an object more than once

results in an error (613) when the transaction is commited: [ObjectDB 2.2.4] javax.persistence.RollbackException Failed to commit transaction: Attempt to reuse an existing primary key value (common.model.UserSession:13) (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:271) at javax.jdo
Issue
2

InternalException

Failed to commit transaction: (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:279) at rbccm.felix.objectdb.workflow.ObjectDbInstanceContainer.commit(Unknown Source) at rbccm.digest ... ) at com.objectdb.o.OBM.bG(OBM.java:719) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:276) ... 9
Forum
2

Is it possible to remove parent/child entities without refresh?

.persistence.RollbackException Failed to commit transaction: (error 613)). Do you have an idea ... .addChild(new ChildEntity().withChildName("childEntity4"));   entityManager.getTransaction().commit ... ();   entityManager.remove(parentEntity.getChildren().get("childEntity1"));   entityManager.getTransaction().commit
Forum
2

OptimisticLockException

with these exceptions: [ObjectDB 2.2.5_04] javax.persistence.RollbackException Failed to commit transaction ... process B lost if process A subsequently commits? 4. Would a valid solution be to explicitly refresh ... - it is acceptable to present an error to the user if it tries to commit changes on a document
Forum
2

pesimistic Lock semantic

that lock could not be granted, quite nice but in that moment I wanted commit the first transaction ... .currentTransaction().commit(); } catch (JDOUserException e1) { pm1.currentTransaction().commit ... () + " --" + "Pesimistic lock succed"); return; } pm1.currentTransaction().commit
Issue
2

Use temporary files to enable very large transactions

to add a new option of using temporary files for flush / commit, as suggested in #6 above (i.e ... us to repeatedly commit on the second database and in case of a fault we can still recover a consistent state.  We run the commit, if the Application consumes a percentage threshold of memory
Issue
2

ArrayIndexOutOfBoundsException on flush

().commit(); } catch(Exception e) { if(em.getTransaction().isActive()) em.getTransaction ... into a commit retry loop which blew out the logs: Attempt to commit a transaction after failure in ... mentioned above is this: [ObjectDB 2.3.2_08] javax.persistence.PersistenceException Attempt to commit
Forum
2

Different behavior with persist() and queried instances?

a sample project, *after* the commit, my list property is correctly enhanced with odb specific fields ... ) it doesn't work. Alex Okay I think I know what's going: After the commit and persist calls I do close the entity manager so my object gets detached. Between the persist() and the commit() call, my list