4 | Replication failed" path="." mode="write" /> <locking version-check="true" /> <processing cache="128mb" max ... Clemens Kunwald It is unclear why you get this exception. Check for additional stack traces in |
4 | Embedding ObjectDB on server application to the ObjectDB home directory. support Support I double checked that ObjectDB.jar is indeed imported into the project...at least on Eclipse. Is there some way I can check on runtime? Still getting this: Message |
4 | Replaying recorded requests... is that your configuration file is not read - you can check it by putting invalid content in ... is not read - you can check it by putting invalid content in the configuration - if no exception |
4 | remove & persist in same transaction => Attempt to reuse an existing primary key value) we check if an Entity (A) with the ID of Entity (B) exist. If it exist we put the date ... and persisting it. But we will check if we can release a quick patch to support this without the workaround |
4 | Server closes if large query runs out of memory of result objects. If you must support very large query result sets, check the temp threshold ... of this parameter is not straightforward and you will have to check its effect on your application. Reducing |
4 | system exception occurred during an invocation on EJB GuestDao one of the tutorial steps. Particularly check your persistence.xml file. If you cannot find the problem try download and run the Maven version of the tutorial. support Support I checked again the tutorial steps |
4 | Failed to read DB file while online backup is running could cause this. Is it a new exception? Can you check build 2.6.2 and 2.6.1 to find the last build ... . Could you please check for more details in the log? support Support You are right I just found the full stack traces in |
0 | com.objectdb.o.InternalException: java.lang.ArrayIndexOutOfBoundsException: null:); log_persisted(e); } protected void persist(Object o) { if (DO_CHECK_REPEAT ... . } if (DO_CHECK_REPEAT_PERSIST) { persisted.add(o |
0 | boolean field flips after schema update (in class) of another field development. If this is a database that you can share with us we can check it. support Support ... . We already have tests that check that schema evolution work, including when fields of all types are added |
0 | [ObjectDB 2.6.9] Unexpected exception (Error 990) Thank you for this report. Could you please check the database file with the ObjectDB Doctor ... database or a database that has no errors in the Doctor check). support Support In DEV after the Doctor |
