19 | Schema Evolution QuestionThe documentation indicates that " In client-server mode the ObjectDB server must be restarted ... must connect to ObjectDB before the restart or whether ObjectDB can be restarted while the client ... the client application was EMPTY. SUBSEQUENT restart of ObjectDB and client after attempting to access |
15 | Modifying something with Explorer -> app JPQL with Enum doesn't work anymore once, but then it didn't happen anymore. I fixed that one with a server(ODB) restart. This doesn't help ... and 3 with this fix)), restart the server through the "restart" feature of the small toolbar icon. After restarting, the next printed number will be proper, without needing to redeploy/run the app |
15 | Failover from Master to Slave: do you have an idea how change the urls when in a Java EE JTA environment without restarting the app ... as master Applications are restarted due to update/maintenance. When they start DB A is selected as ... when it comes online again. In this way, even though applications are restarted, ObjectDB |
15 | javax.jdo.JDOUserException Failed to locate field field exampleField using reflection (error 363) to restart the Application (ODB Client), and we have client-server mode only in testing environment now, so we just configured the services to restart automatically up to 5 times and we lived with that. But now we added a field to BDO class which is parent class for many others, and now it needed 6 restarts |
13 | Recommendation - concurrent access multiple class v Currently schema changes require server restart, as well as restarting the application with the new ... , changing the schema requires restarting all of them with the new version of your application. With some ... application server for a short time when there is a low load, you can restart that application server |
13 | best practice for DB recovery instance, restart the failed instance and then enable writes again(that will be controlled in the DAO ... we would have to restart the slave DB in master mode, is that correct? Or is there a way to start writing to the replica DB without restart? We need to ensure that we don't have unplanned outages, so we need some |
3 | Server out of memory exceptions. When all threads have exited (i.e. the application shutdown) the loop restarts. There shouldn't ... occurs after I restart the server & test without clearing the databases, i.e. I let the test run for 20mins; stopped the test; restarted the server; restarted the test; the exception came after running |
3 | Internal Exception and Index Problems the super class). You can avoid this issue by restarting the ObjectDB server after every such schema change. Future versions of ObjectDB may support schema changes without restarting the server, or at least should produce better error messages in these cases. Currently the direction is to restart |
3 | each 1-2 days objects on some objectdb level lock/block each other-Georg Zwicker it was not more possible to create a heap dump, we even had to restart the complete ... the up to date 60GB database could also help. support Support attached heap dumps after restart (for sure now ... (restart of our core system including version 2.7.5_03 together with adding some more indexes, indexing |
2 | Unexpected exception (Error 990) you get this exception after changing the schema? If the schema has changed, was the server restarted before using the new schema? After restarting the server, do you still get this exception? support Support Thanks a lot for the fast reply. Restarting the objectdb server indeed solved the exception |
