5 | ODB IndexActivation NullPointerException ObjectDB feature. Build 2.6.7_07 includes an attempt to fix this exception. Please try it. support ... EmbeddedSystems Please try build 2.6.9_08 that should fix the NullPointerException. remove the printing ... and waited for a new version to fix. Unfortunatly the new version 2.7-1_01 does not fix that problem as |
5 | Doctor fails to run when running in parallel on more DB files. -Djava.io.tmpdir=$tmpdir -cp objectdb.jar com.objectdb.Doctor file1.odb fixed/file1.odb&\ java -Xmx100G -Djava.io.tmpdir=$tmpdir -cp objectdb.jar com.objectdb.Doctor file2.odb fixed/file2.odb&\ java -Xmx100G -Djava.io.tmpdir=$tmpdir -cp objectdb.jar com.objectdb.Doctor file3.odb fixed/file3.odb |
5 | Unable to convert 1.x odb file to 2.x. Please try build 2.5.5_04 that includes an attempt to fix them. support Support Thanks for the fix ... the value in the HashMap. Can this be fixed too? jakab Gergely Jakab This map issue would be much more difficult to fix, since no exception with a stack trace is available now. Therefore, we may need |
5 | NegativeArraySizeException on commiting a transaction, but the same error is happening also on the fixed DB file. Btw. during fixing the DB file an Internal error was thrown (details here: http://www.objectdb.com/database/issue/285 ), but the fixing went ... Thank You for the fix. We will consider reorganizing our data structures, but with this raise we will have enough time to plan it carefully. jakab Gergely Jakab |
5 | Possible cause for "Enhancement of type ... is old and cannot be used" to fix it in build 2.6.6_08. I reported today on investigations by version here: http://www.objectdb.com ... a TableGenerator. That problem was demonstrated by the provided test case, fixed in build 2.6.6_08 ... at all in my main real-world web app). webel Dr Darren Kelly The bug was found and fixed in build 2.6.9_01 |
1 | Unexpected exception (Error 990) on find limit. Stefan Stefan Mair There was a problem with using large objects in the past, but it was fixed ... it seems that you are experiencing a new problem. Apparently progress in fixing ... 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 | Enhanced classes problem In order to understand and fix the problem, could you please provide some information ... Maruta M Sedlakova We succeeded in reproducing the problem and hope to have a fix soon ... .5.0_06 should fix both problems: Array ([]) relationship are now always excluded from |
1 | Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct) of my time. Please attend to this as soon as possible and fix this carefully. I look forward to having this fixed and to having a robust ObjectDB working on my problem, as I am greatly encouraged by ... ; } } support Support Setting fetch=FetchType.EAGER on 'ownedElements' does seem to fix it (the lists load |
1 | ObjectDB 2.2.3 to the bundled examples. Fixed a schema evolution bug in renaming user types. Fixed a bug in handling schema evolution (regression of 2.2.0). Fixed a bug in queries on large objects. Fixed a bug in using persistent properties with incomplete enhancement. |
1 | ObjectDB 2.4.7Fixed bugs in cascading merge and refresh. Fixed an internal java.lang.ArrayStoreException bug (com.objectdb.o.InvToOneLoadRequest). Fixed a regression bug (starting 2.4.4_13) in handling embeddable types. Fixed a performance regression (since 2.4.4_01) in query result retrieval. Added INFO level |
