11 | Memory Leak in EntityManagerFactory ? it. Anyway, if this diagnosis is correct then a possible solution on your side may be to check and commit |
11 | Queries are slow on a large database have to be retrieved. For diagnosis please try the same query without the ORDER BY clause. A composite |
11 | Query becomes slower on moving from ObjectDB 1.x to ObjectDB 2.x Binit Bhaskar The Doctor itself can diagnose problems in the database (when running in diagnosis mode |
11 | 500Mb ObjectDb database opening issue it again on our computers? Since the problem happens in your environment we will have to continue with diagnosis |
2 | InternalException in Database Doctor when the database is opened by the Doctor during diagnosis. This is disabled now in build 2.6.9_08 |
2 | Querying error - java.lang.ClassCastException: com.objectdb.o.STV the Doctor in diagnosis mode). Check if your application can bring the database again to a state in |
2 | [ObjectDB 2.3.7_25] Unexpected exception (Error 990)] null lorenz2304 Benjamin Lorenz You are right. The previous fix handled only diagnosis mode and a new |
2 | database corrupt with you on diagnosis of this issue, but we will need more information. For example, does |
2 | Errors in log to repprt. If you want to be sure you can run the Doctor in diagnosis mode first (possibly on a recent backup |
2 | Page cache File handling produced an java.io.IOException: Negative seek offset:745) btc_es BTC EmbeddedSystems Build 2.6.7_02 adds some diagnosis checks in order to produce |
