Internal Website Search

. However, after transaction.begin ... persist(p) .. commit of a new object, my client program can no longer ... then this could be a cache issue with a simple solution (e.g. changing flush mode from commit

Hi, we started to get a java.lang.NegativeArraySizeException from ObjectDB upon changing an object in the DB and committing the transaction. I tried to repair the DB file ... > Can you update this specific object (and commit) after emptying its string fields?

We have following issue, if we execute a commit: java.lang.StackOverflowError at com.objectdb.o.ENT.D(ENT.java:411) at com.objectdb.o.ENT.D(ENT.java:499) at com.objectdb.o.ENT.D(ENT.java:417) at com.objectdb.o.ENT.D(ENT.java:499) at com.objectdb

Hi, I have one case where commit (update of entity in this case) is not taken in account unless database is actually closed and re-open, no error. I tried to use flush instead of close+re-open but it does not work. So currently there is a dirty close + open

[ObjectDB 2.4.6_10] javax.persistence.RollbackException Failed to commit transaction: Java

Is it possible to query and commit on the same persistence manager (i.e. same odb file) at the same time? jake Jake Hang Multithreading is fully supported by ObjectDB, so you can query and update the database at the same time using multiple threads.

Git seems not to commit objectdb.conf

Memory error during commit, if @ElementCollection field contains many elements

I get the following on commit:  (v2.3.7_15) Let me know if you need more info. Caused by: com.objectdb.o.InternalException at com.objectdb.o.InternalException.f(InternalException.java:236) [:] at com.objectdb.o.SPW.aq(SPW.java:109) [:] at com

and the database: 37 pm.currentTransaction().commit(); 38 pm.close(); 39 ... transaction, is expected to be stored physically in the database when the transaction is committed (line 37 ... >On transaction commit (line 37), new persistent objects (like a new ArrayList