8 | ObjectDB size not reducing file. support Support Thanks. So even though the DB is not corrupt I will run it like I'm repairing |
8 | Using the wrong class to access a database; it now reports zero entries -> db is corrupted If it is an error to use the wrong class to access the db |
8 | doctor error message after database getting page errors -------------------- [1] Free page list is broken Here is a link for the corrupt database: https://www |
1 | Unexpected exception (Error 990) on find that was fixed now in version 2.7.1. The new version fixes a critical bug that in some cases (rare but possible) may cause database corruption. support Support |
1 | ArrayIndexOutOfBoundsException: -1. Therefore it could corrupt the database, as demonstrated by your test. Consequently many types of unexpected exceptions |
1 | java.lang.NullPointerException during access a field, only if the classes enhanced fixes a critical bug that in some cases (rare but possible) may cause database corruption |
1 | Explorer bug ? Objects seem to be missing from database in Class view, but are present as referencesobjectdb-2.2.5_08 NetbeansID6.9.1+Glassfish3.01 I suspect the following is an Explorer bug. It is marked knowingly as CRITICAL by me because it makes the ObjectDB system unusable for a real project because it appears to be either database integrity corruption, or it just looks like |
1 | Server out of memory exceptions for 10mins. Is it possible something could be corrupted during the restart? Is some state held |
1 | log entry and massive performance issues that the database is somehow corrupt (we did the last repair last ween with 2.7.4_02 Doctor)? In addition |
1 | ObjectDB 2.7.1Fixed a critical bug that may cause database corruption (issue #1977). Improved error messages on entity operation exceptions. Fixed a NullPointerException on cascading persist throw an unloaded collection (issue #2049). Fixed the location of a temporary file for index update (issue #2050). Fixed |
