About restart

1-10 of 99Refresh
Manual
94

Database Server

. Usage: java com.objectdb.Server [options] start | stop | restart options include: -conf java -server -Xmx512m com.objectdb.Server start Stopping and Restarting To stop ... and then immediately start it again, use the restart command: > java com.objectdb.Server restart
Forum
34

Replication error on slave restart

previously. I have copied database file to slave... and so on by manual. It worked fine. But if I restart ... and then restart, I will get: java.lang.NullPointerException at com.objectdb.o.RPR.u(RPR ... only once when installing the replication. Every time you restart the master server a new recording file
Forum
33

ODB should auto-restart if it detects it's necessary

Hi! I find very tricky the need to restart ObjectDB server after schema modifications in ... objectdb.config) that each time ObjectDB detects a schema change that requires restart, it should automatically restart itself. This way we save a lot of headaches from our dev. ops. Currently
Tutorial
19

Step 1: Install BIRT and ObjectDB Driver

, and finally approving the installation and restarting the IDE. Installing the ObjectDB Data Source Driver ... the installation and restarting the IDE. Note: See this issue regarding matching the driver version
Manual
13

BIRT/ODA ObjectDB Driver

the license agreement, clicking Finish, and finally approving the installation and restarting
Manual
13

Database Schema Evolution

, have to be converted to the new schema. Note: In client-server mode the ObjectDB server must be restarted
Tutorial
13

Step 7: Run the Spring Web App

. Right click the server node and select Restart. When using GlassFish - on the fly enhancement (weaving
Result
13

ObjectDB Object Database Features

. Can also be managed (started, restarted, stopped) from the command line. Class Enhancer Boosts
Forum
3

Schema Evolution Question

The 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 ... was EMPTY. SUBSEQUENT restart of ObjectDB and client after attempting to access with new schema caused
Issue
3

Internal Exception and Index Problems

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 the server