Home » Search

About flush

61-70 of 128Refresh
Issue
2

Internal exception

relationship, which required a flush before running the mapped by query (due to changes since last commit/flush) in order to retrieve the mapped by instances. The stack trace indicates a failure to cascade persist operation from unknown reason during that flush. Any more information could help
Issue
2

objectdb-2.6.9_06: Extended Persistence Context fails: 'Attempt to begin a new transaction when a transaction is active'

.persist(o); if (Global.USE_OBJECTDB) { em.flush(); //ObjectDB ensure id ... //Attempt to flush a transaction when no transaction is active (error 611 ... .TransactionRequiredException Attempt to flush a transaction when no transaction is active (error 611
Forum
2

Performance in large transactions

in order to apply changes to the database on flush/commit. This could be done by keeping a copy of every managed object and comparing copies to actual objects on every flush or commit ... and requires comparison on every flush. To avoid this, we introduce now a new method, con.objectdb
Forum
2

Querys slower when execute a query after every persist

classes are not enhanced every flush or commit requires comparison of object states in order to find which objects in the persistence context have been modified and should be flushed to the database ... requires a more expensive flush). Results of your test with enhanced classes are much better and proportional: start 682 6232 btc_es
Forum
2

SectionClassifier message in log

the application on object retrieval is: Caused by: rbccm.felix.framework.ApplicationException: Error flushing queue at rbccm.felix.objectdb.messaging.ObjectDbMessagePipe.flush(Unknown Source) at rbccm.felix.objectdb.messaging.ObjectDbMessagePipe.flush(Unknown Source) ... 42 more Caused by: java.lang
Forum
2

Spring Transactions (@Transactional) within ObjectDB

advise !   Thanks, Sandeep Build 2.5.2_01 adds support for enabling auto flush by default, by setting a system property:     System.setProperty("objectdb.temp.auto-flush", "true"); before loading ObjectDB, or as a JVM argument: > java -Dobjectdb.temp.auto-flush=true ... Sandeep
Forum
2

Heap Limit reached although the option 'objectdb.temp.page-file' is activated

although the flush and the GC were invoked regularly. The attachments show the memory heap dump ... ] at com.objectdb.o.OBM.bO(OBM.java:835) ~[na:na] at com.objectdb.o.OBM.flush(OBM.java:765) ~[na:na ... and move modified database pages (after flush) to a temporary file, but is not related to entity
Issue
2

com.objectdb.o.InternalException: java.lang.ArrayIndexOutOfBoundsException: null:

.USE_OBJECTDB) { em.flush(); //ObjectDB ensure id exists ... ownedElement) { if (DO_PRE_FLUSH) { em.flush(); } if (owner
Forum
2

remove() and persist() in same transaction => Attempt to reuse an existing primary key value

); // If we call a FLUSH it works. // em.flush(); System.out.println("create and persist ... int id; } } A possible workaround, that this scenario works is to call a flush (see commet
Issue
2

NoResultException: No matching results for a unique query

to the query until commit. This behavior can be changed by modifying the flush mode. Which flush mode are using? Hi, I didn't change it so I am using the default Flush Mode (COMMIT). I don't