5 | Exception after update of indices of Entity class.ClassCastException: com.objectdb.o.PIX cannot be cast to com.objectdb.o.FIX at com.objectdb.o.EIX.<init ... ) at java.lang.Thread.run(Thread.java:748) Is there any way to fix this? Best regards, Markus Ritter ... .ClassCastException: com.objectdb.o.PIX cannot be cast to com.objectdb.o.FIX at com.objectdb.o.EIX |
1 | ClassCastException during query move the enum class into the entity package, this has organization reasons. And I tested your fix with the last ObjectDB patch 2.7.6_02, but the fix does not work. We got the same exception as before. I ... EmbeddedSystems > And I tested your fix with the last ObjectDB patch 2.7.6_02, but the fix does not |
1 | References to objects of missing obsolete entity classes(EMF.java:149) btc_es BTC EmbeddedSystems It is unclear how this new issue is related to the fix ... for a database, so if possible, is is recommended to try fixing the database by running the Doctor. A possible ... was indeed removed. >> This is abnormal state for a database, so if possible, is is recommended to try fixing |
1 | ObjectDB 2.8.5Fixed a bug in using AS in SELECT NEW (breaks some Spring Data JPA queries). Fixed a bug in tracking changes to new collections after flush (issue #2640). Fixed a StackOverflowError on no access permission to objectdb.conf (issue #2643). Fixed a bug in managing pessimistic locks after using |
1 | ObjectDB 2.2.4 in criteria queries. Improved Explorer performance by disabling EAGER fetch. Fixed critical bugs in using flush. Fixed bugs in cascading merge. Fixed a multithreading deadlock bug. Fixed a bug in using JOIN FETCH with DISTINCT. Fixed Metamodel API's getTypeId method to support single ID field. |
1 | Out of Memory - Slow leak?This is a continutaion of Issue 61 - unfortunately it doesnt seem that the fix in 2.2.9_03 has fixed the problem. The scenario is still the same: I have two "producer" processes which insert messages ... Szurgot The fix of issue 61 fixed an important memory leak but unfortunately it seems that it is not |
1 | ObjectDB 2.2.2Changed log format to include date and time. Changed class loader management. Fixed handling multiple order expressions in inverse (mapped by) fields. Fixed the behavior of CacheStoreMode setting in L2 shared cache. Fixed TreeSet and TreeMap element comparison bugs. Fixed an Explorer bug in opening |
1 | Explorer bug ? Objects seem to be missing from database in Class view, but are present as references.BooleanValue [null](TEST: A readonly fixed true Boolean value) INFO: RequestBean []: Persisted: com.greensoft.entity.value.BooleanValue [64](TEST: A readonly fixed true Boolean value) INFO: RequestBean []: Updated: com.greensoft.entity.value.BooleanValue [64](TEST: A readonly fixed true Boolean value |
1 | Negative snapshot user count exception may be relevant: Your move from ObjectDB 2.3.x to 2.5.2. Corruption of the database that cannot be fixed by ... . Rolling back to 2.3.x would be a problem because development work I did this year relies on fixes ... , but they are not seen in the log after that restart, so hopefully the Doctor fixed these index issues. In |
1 | ObjectDB 2.6.8 of pessimistic locks on client-server connection failure. Fixed an OptimisticLockException bug on commit after flushing a removed modified entity object. Fixed a NullPointerExeption on new index building. Fixed a NullPointerExeption on flush (issue #1840). Fixed a bug in using temporary files in large |
