7 | Error using query with MAX() function about the Doctor errors than the query exception. Please keep running the Doctor frequently to verify |
7 | Filename.odb$ Persisting Issue If emf this is the only EntityManagerFactory instance in your application verify that emf.close |
7 | Database is erased after deploying a new web application version stack trace. What is in line 28 at that class? Please also verify that you close |
7 | Activation error on Schema change, and actually any change to your schema may cause a similar exception. Please verify |
7 | explorer locks local database in readonly modehi, my current use case is: execute unit test, verify results in explorer. my problem, i have to close the explorer before every run, and open it again after the tests are done. this slows down the whole process. i opened the database in readonly mode, but the file will be locked by the explorer |
1 | combined index not used above) after this action we can verify that it contains statistics as expected. Please report |
1 | JDO PersistenceManager.getSequence() returns null sometimes package; you can verify that it is being read at run-time by introducing an error such as an invalid |
1 | objectdb seems to do explicit gc which leads to excessive CPU usage verified now by a search in the entire ObjectDB source code (calls to gc were found only in our tests |
1 | Server crash - Mismatch client-server protocol prefix here, but just verify by running the Doctor that it is healthy. A thread dump of the server |
1 | javax.servlet.ServletException: Annotated methods must follow the JavaBeans naming convention. __odbHidden_getPropertyName exist anymore in build 2.2.6_01. Please verify that: You are using only the new ObjectDB jar |
