4 | NPE when getting Persistence manager at: fixed/./private.odb [./private.odb] Took 20 seconds Filesize before: 495M ./private.odb Filesize after: 489M fixed/./private.odb Could You please advice us what to do ? jakab Gergely ... schema upgrade, which might be be fixed by now. It may possibly be solved if you update your entity |
4 | DB Doctor with Recording enabled and using Database replication, that we need in that case delete recording data, and copy fixed file manually also to all slaves? Or is there any simpler way? thamal Tomas Hamal Yes, if you run the Doctor to fix a database, i.e. create a new database file, you will have to start the replication again with a copy of the new (fixed |
4 | Attempt to open a non existing file '/tmp/objectdb_xxxx/SortQueryItr_6.mrg' to the JVM, and post an update about the results. support Support Thanks a lot - my guess is that 2 will fix ... have been running my 5 applications for more than 24h and the error is gone with fix 2/ so the fix works |
4 | ClassCastException on closing PersistenceManager explicitly you may be the only user affected. Build 2.6.4_01 includes an attempt to fix this exception ... now the new build of objectDB with the fix. jakab Gergely Jakab #3 stack is the same issue. Unfortunately this is the risk of being the first to use a new feature. support Support With the fixed |
4 | ArrayIndexOutOfBoundsException and then to fix it. If it doesn't help - you may have to delete that specific entity object to make ... ) it may help in understanding and fixing the problem. support Support Hi, I have restarted objectdb server ... the messages are replaced, it should be "has 0 entries instead of 280", and it will be fixed). support |
4 | Corrupted Database or error in ObjectDBExplorer?. This may fix the database. Please check and update. support Support Hello, the work around solves ... . But before it was set. Any idea? Another point: Can we hope for a fix? Because the multi steps to open ... can delete the value of that field. support Support Thanks, the fix solves the issue btc_es BTC EmbeddedSystems |
0 | Server out of memory exceptions that should fix this. If it doesn't - try to disable the query program cache (and maybe also the query result ... regarding the new build that may fix the memory leak would be appreciated. support Support So far so good ... . felixobjectdb Richard Szurgot Thank you for the update. This issue will be marked now as fixed |
0 | ObjectDB 2.1.1Fixed an Explorer bug in handling listeners and callbacks. Fixed a bug in using user/password url arguments multiple times. Fixed several bugs in query processing and running. |
0 | Internal exception when quering 2.5.1. Could you provide us fix or some advice? If more info is needed, we can provide it. Thank ... ? support Support Yes, you are right. When do you plan to fix this issue? We would like to avoid checking ... _01 should fix this bug (which is a duplicate of issue #1107) support Support Build 2.7.2_01 |
0 | boolean field flips after schema update (in class) of another field that fixed that issue. support Support I think the schema may changed 2-5 times during the last ... - this is something which should never happen for a database. We don't really know if it is fixed in 2.8.4, as we cannot reproduce in ... this is the rare issue related to schema evolution that was fixed in version 2.8.4. support Support |
