8 | multi thread application, id field sporadically null to overcome the problem by using flush(), clear() and refresh() hgzwicker Hans-Georg Zwicker Good. See also this manual page, regarding setting a flush mode. support Support |
8 | calling persist on an object more than once is invoked, or the EntityExistsException or another PersistenceException may be thrown at flush or ... the database is only performed on commit or flush. support Support |
8 | Query for objects persisted within the same transaction was persisted. lwalkowski Lukasz Walkowski You may change the default flush mode: https://www.objectdb.com/java/jpa/query/setting#Flush_Mode_setFlushMode support Support Thanks, The part about performance in |
8 | Performance issue in a query due to internal calls visitRefs and visitKeyRefs is spent on a flush operation before the query is executed. Apparently you have pending changes ... with the pending changes in memory (before commit) then a flush operation is required before the query |
1 | ObjectDB-2.6.9: Failed to commit transaction: Failed to set numeric value of field property Element.id using reflection reflection (error 363) at com.sun.enterprise.container.common.impl.EntityManagerWrapper.flush ... .flush(OBM.java:772) ... 117 more Caused by: java.lang.reflect.InvocationTargetException ... webel |
1 | ArrayIndexOutOfBoundsException: -1.o.OBM.flush(OBM.java:739) ... 1 more Caused by: java.lang.ArrayIndexOutOfBoundsException ... situations (e.g. when using flush that is followed by other operations and then commit) - the page |
1 | Persist & remove in same transactionI have a test case (attached) which performs the following actions: Open a new transaction Create & persist a simple entity object, EntityManager is flushed, Transaction is not committed Count ... Remove the entity object, EntityManager is flushed & cleared, Transaction is not committed Count |
1 | Best practise loading big data again. What us bothers is that currently we have no other chance then to cut transitions or flush or ... some auto-commit/rollback/flush/reconnect strategy but it would be definitely better |
1 | ObjectDB 2.6.8 after flushing a removed modified entity object. Fixed a NullPointerExeption on new index building. Fixed a NullPointerExeption on flush (issue #1840). Fixed a bug in using temporary files in large |
1 | GC Memory into objectdb, the EntityManager is flushed and released. This process is repeated until all 16 ... flush. So bulk load of data into the database should be done in smaller transaction (with begin |
