8 | Failed to resize file - file system limitation error in ObjectDB or a corrupted database file. Therefore, you might be able to debug it externally |
8 | objectdb-2.6.9_02 (with "objectdb.temp.no-enhancement-crc-check") vs. generic classes with interfaces: detailed investigation enhancement from Clean and Build has not been corrupted. - No javaagent enhancement is used at any |
8 | ODB lost?I'm new to ObjectDB. While debugging small programs in single-step mode in NetBeans, the ODB appears to get corrupted or lost if I don't invoke close on EntityManager. If I re-run my program and get a new EntityManager, the instance behaves as if the data that was persisting is somehow gone. I |
8 | Unexpected exception (Error 990) file. You can find a list of possible reasons for database corruption on the link |
8 | Java 9 support incompatibility and cause some database corruption. So I created my own javax.jdo Java 9 module |
1 | EOFException is corrupted and you must repair it using the ObjectDB Doctor before you can use it. Otherwise, many different |
1 | NullPointerException in ENH.g(ENH.java:401)Hello, corresponding to your suggestion I created a private ticket in reply to http://www.objectdb.com/database/forum/1109. Attached you will find my database file (I removed most of the content but one corrupt instance is still included). I error happens when reading the field "Event.participants |
1 | ObjectDB 2.3.7Fixed a critical issue that may cause database corruption (issue #630). Initial attempt to enable navigation through lazy loading from detached objects (feature request #326). Improved toString of criteria queries to use aliases (issue #127). Fixed automatic variable naming in criteria queries |
1 | [ObjectDB 2.6.9] Unexpected exception (Error 990) corruption, so it is highly recommended to use the new build. support Support |
1 | stress test -> com.objectdb.o.InternalException: null. It seems that all entity managers become corrupted / broken. (see stack trace below) Should it be something in |
