11 | Spring Transactions (@Transactional) within ObjectDB Sandeep Sandeep Dhamale 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 ... support Support |
11 | Querys slower when execute a query after every persist EmbeddedSystems When entity classes are not enhanced every flush or commit requires comparison ... and should be flushed to the database. If you have more objects in the current transaction it takes more time (i.e. every query execution requires a more expensive flush). Results of your test with enhanced |
11 | remove & 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 AGAIN"); // create ... id; } } A possible workaround, that this scenario works is to call a flush (see commet) after em |
11 | 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 ... .flush(OBM.java:765) ~[na:na] btc_es BTC EmbeddedSystems The heap dump shows millions of entity objects ... seem related to objectdb.temp.page-file, which may work and move modified database pages (after flush |
9 | Error using query with MAX() function If you are using EntityManager's flush you should try build 2.2.3_04 that fixes a critical bug ... the manual. if( (count % config.getUpdateFreq()) == 0) { em.flush |
9 | Duplicate Entity class names causes Exception in Query.numberOfMapItems"); //ObjectDb demands we flush transaction to db if we wish to see its results q ... demands we flush transaction to db if we wish to see its results q.setFlushMode(FlushModeType.COMMIT |
2 | ObjectDB 2.2.6Fixed the "Attempt to reuse an existing primary key value" after flush bug. Fixed a bug in tracking changes to collections of new flushed entity objects. Fixed generated value (ID allocation) bug with flush and in EJB containers. Fixed a NullPointerException on getObjectsById. Fixed a server freeze |
2 | NoResultException: No matching results for a unique query modifying the flush mode. Which flush mode are using? support Support Hi, I didn't change it so I am using the default Flush Mode (COMMIT). I don't get why this is happening, it just has happened |
2 | objectdb-2.6.9_06: Extended Persistence Context fails: 'Attempt to begin a new transaction when a transaction is active'(o); if (Global.USE_OBJECTDB) { em.flush(); //ObjectDB ensure id ... .TransactionRequiredException //Attempt to flush a transaction when no transaction is active ... .persistence.TransactionRequiredException Attempt to flush a transaction when no transaction is active |
2 | com.objectdb.o.InternalException: java.lang.ArrayIndexOutOfBoundsException: null:_OBJECTDB) { em.flush(); //ObjectDB ensure id exists ... ownedElement) { if (DO_PRE_FLUSH) { em.flush(); } if (owner |
