Shutting down the system In an embedded environment, when an application shuts down, it should first shut down . Shutting down the system

If the application that started the embedded quits but leaves the Java Virtual Machine (JVM) running, continues to run and is available for database connections.

In an embedded system, the application shuts down the system by issuing the following JDBC call:

DriverManager.getConnection("jdbc:derby:;shutdown=true");

Shutdown commands always raise SQLExceptions.

When a system shuts down, a message goes to the error log:

2008-08-07 19:23:00.508 GMT: Shutting down instance 80000001-00d0-8bdf-d115-000a0a0b2d00

Typically, an application using an embedded engine shuts down just before shutting itself down. However, an application can shut down and later restart it in the same JVM session. To restart successfully, the application needs to reload org.apache.derby.jdbc.EmbeddedDriver as follows:

Class.forName(org.apache.derby.jdbc.EmbeddedDriver).newInstance();

Loading the embedded driver starts Derby.

The JDBC specification does not recommend calling newInstance(), but adding a newInstance() call guarantees that will be booted on any JVM.

It is also possible to shut down a single database instead of the entire system. See . You can reboot a database in the same session after shutting it down.