6 | ObjectDB stability after power failureI'm considering using ObjectDB in a system that is going to be running continuously without support instantly available for many years. How stable is ObjectDB when it comes to power failures and unattended restarts? Is database integrity maintained during such events? I have seen database vendors |
6 | Connection is closed Caused by: java.io.EOFExceptionI am getting this exception on a regular basis, after a period of time of repeating the same code execution. I don't understand why. I restart the DB server and my code works again for another period of time until same exception is encountered again. I cannot pin down a pattern e.g. after a certain |
6 | Internal exception in objectdb-2.4.4_17.jar. Do you still get the exception after restarting the server? You should also check the database by |
6 | newbie - lots of exeptions of switching an ObjectDB version at the client side and keeping the server running. Try restarting the server |
6 | Memory Leak in EntityManagerFactory ?. With really big databases some customers told us that they need to restart the server after some |
6 | objectdb got hang after fetch some record. restarting the server and waiting to some other threads to complete. This waiting was restricted now |
6 | Date field Index is corrupted due to time change. Restarting the application does not help. Also, dbDoctor does not fix the problem. You can verify this by |
6 | Vacuum - Reclaiming Unused Space In Odb. Even if there is a failure, restarting the slave and the connection to the master should complete all missing |
6 | Indexing a field results in internal Exception. If you are working in client-server mode, you should try to restart the server after schema change |
1 | Memory leak in com.objectdb.o.CST. Anyhow, before I shut the server down for restart I took a cpu profile snapshot of objectdb. It was all JVM |
