About restart

81-90 of 101Refresh
Forum
1

recovery enabled="false", still creates tablename.odb$ files

Running in embedded mode, configuration specifies "".  Still, tablename.odb$ files get created, and if still present after an abrupt stop, the application will not restart properly.   What do we need to do to not utilize recovery files (not have orphan tablename.odb
Forum
1

Recovery file does not match db file

it and restart the database server. Version 2.3.1 is nearly one year old - you should upgrade your server
Forum
1

Replication not working anymore

for reproducing this new issue? I got this stack trace when enabling recording on slave server and restarting
Forum
1

Retrieving Metamodel without connection

restart tomcat. Other JPA providers are able to fetch the Metamodel without connecting to the DB. I
Issue
1

Retrieving Metamodel without Connection

restart tomcat. Other JPA providers are able to fetch the Metamodel without connecting to the DB. I
Forum
1

SectionClassifier message in log

it was deleted when the application was restarted. I'll try to keep a copy if/when it occurs again. I imagine
Issue
1

Server crash - Mismatch client-server protocol prefix

We'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
Issue
1

Service terminated silently (crashed?)...is there any way to cause a crash dump?

on port 6138. ObjectDB Server started on port 6138.  <--This is where I restarted the service.   Note
Forum
1

Stacktrace in Explorer when running query

Explorer view settings) and then restart the Explorer. Hello, that solved the problem, works like a charm now. Thank you very much. Alex alexweirig
Issue
1

stress test -> com.objectdb.o.InternalException: null

the errors mentioned above start to happen, after a short while, I have to restart Tomee