About commit

181-190 of 200Refresh
Forum
1

Attempt to remove a detached entity object (error 613)

to merge it ... Unfortunatly, i get this error : Failed to commit transaction: Attempt to remove a detached entity object (error 613)      at com.objectdb.jpa.EMImpl.commit(EMImpl.java:290) We see in this stack trace that is a commit operation, all right ... So why does it try to remove the object
Forum
1

ClassCastException: cannot be cast to com.objectdb.spi.TrackableUserType

.makePersistent( instance ) transaction.commit() } catch( e ... .OBM.bE(OBM.java:715) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:274) at javax.jdo.Transaction$commit.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall
Forum
1

Database Inconsistency or corruption

() + 1);     System.out.println("Trying to commit");     em.flush();         System.out.println ... . It is unclear why your updates are not committed. Here is a list of possible reasons: Changing objects with no active transaction. Updating objects in a transaction but with no commit. Partial
Forum
1

Database(*.odb) file size on disk

);     entityAIds.add(entity.id);     em.getTransaction().commit();    }    System.out.println("references ... .class, entityAIds.get(i));     entity.entityB = entityB;     em.getTransaction().commit ... ));     em.remove(entity);     em.getTransaction().commit();    }   }   em.close();   emf
Forum
1

Empty temporary dat files in the temp folder

, begin a transaction, do some stuff (find, persist, remove …) and then commit or in the case of errors ... ().commit();   em.close();   emf.close(); } public static void acessDB(String db ... ().commit();   em.close();   emf.close(); } @Entity public static class MyEntity {   @Basic
Forum
1

Entity Update - Is the documentation up to date?

transaction.  If I subsequently begin and commit a transaction, all my changes seem to be merged ... from outside an active transaction.  If I subsequently begin and commit a transaction, all my changes ... will also be applied to database on transaction commit. I'd like to understand the "dirtying" of entities
Forum
1

Error 363 - Failed to read value of inverse relationship

.JavaEETransactionImpl.commit(JavaEETransactionImpl.java:453) at com.sun.enterprise.transaction.JavaEETransactionManagerSimplified.commit(JavaEETransactionManagerSimplified.java:867) at com.sun.ejb.containers ... );             tr.commit();         } catch (Exception ex) {             ex.printStackTrace
Forum
1

Extra uninitialised entities spawned on merge()

, "root");         em.persist(root);         em.getTransaction().commit();         Long id = root ... );             em.getTransaction().commit();         }         em.getTransaction().begin();         em.merge(root);         em.getTransaction().commit();         TypedQuery query = em
Forum
1

find() cost unreasonable time!

, (System.currentTimeMillis()-start)/1000f);     trans.commit();     em.clear();     trans.begin();    }   }   trans.commit();   System.out.printf("Total: %d, Level:%d %n", iNum, iLevel);   float timecost ... , that is a big problem. After commit everyone can see the changes. Sometimes a refresh is needed
Issue
1

GC Memory

: Persisting too many large objects in one transaction. Note that only commit can release memory, not ... and commit for each, and possibly also clear after commit) Using classes that are not enhanced. In