Internal Website Search
61-70 of 74 resultsRefreshFailed to resize file - file system limitation error rather than a bug in ObjectDB or a corrupted database file. Therefore, you might be able to debug | |
objectdb-2.6.9_02 (with "objectdb.temp.no-enhancement-crc-check") vs. generic classes with interfaces: detailed investigation have also used UNIX file timestamp checking to ensure enhancement from Clean and Build has not been corrupted | |
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 | |
Unexpected exception (Error 990) database file. You can find a list of possible reasons for database corruption on the link | |
Java 9 support incompatibility and cause some database corruption. So I created my own javax.jdo Java 9 module | |
EOFException> The database file that you uploaded is corrupted and you must repair it using the ObjectDB Doctor | |
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 | |
ObjectDB 2.3.7 Fixed 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 | |
[ObjectDB 2.6.9] Unexpected exception (Error 990) corruption, so it is highly recommended to use the new build. support Support | |
stress test -> com.objectdb.o.InternalException: null, because none of the DB queries work after those errors. It seems that all entity managers become corrupted / broken |