9 | log problemHi we have found that when restarting the database in contrast to making stop/start database log doesnt contain any data. Does anyone have similar issues. regards. peric.emil Emil Perić Restarting the server should have the same effect as stopping the server and then starting |
9 | Extending model by "common entity" is unexpected. Maybe you have to restart the server (I see that the stack trace is generated by ... this exception. support Support Restart didn't help at all. I will prepare test case and submit |
6 | Complex Schema Upgrade not working-Server has been properly restarted. All other classes which just had package renames are working |
6 | Low performance when getting grove roots. support Support Yes, it happens on a new database. Moreover, if I comment the @Index line and restart |
6 | Guestbook Tutorial (Eclipse/Glassfish). At some point, may be when restarting Glassfish or re-publishing the application, the database |
6 | Explorer in 2.3, allow to close individual or all. c. Buttons to restart database, hot backup (remote server to local |
6 | Failed to commit transaction: Attempt to commit a rollback only transaction of locking problem, but for some reason it persists across database restarts, which is scary |
1 | Can't open replicated database and still got the error but when I restarted the objectdb servers and the application clients |
1 | Server crash - Mismatch client-server protocol prefixWe've been having a problem where our ObjectDB server goes unresponsive every 2 days or so. I've reviewed the server-side logs, and there are no events logged shortly before the crash. Once the server gets in this state, it is unresponsive to bin/server.sh restart; I have had to reboot the entire |
1 | File lock exception on odb$ had assumed that objectdb would reprocess these when the services restarted but instead we got the exception |
