Shutting down Derby or an individual database

jdbc:derby:;shutdown=true

A successful shutdown always results in an SQLException to indicate that Derby has shut down and that there is no other exception.

If you are running with a security manager on JDK 8 or higher, you must grant Derby permission to deregister the embedded driver in order to fully shut down the system. See "Configuring Java security" in the Derby Security Guide for details.

If you have enabled user authentication at the system level, you will need to specify credentials (that is, username and password) in order to shut down a Derby system, and the supplied username and password must also be defined at the system level.

You can also shut down an individual database if you specify the databaseName. You can shut down the database of the current connection if you specify the default connection instead of a database name (within an SQL statement).

// shutting down a database from your application
DriverManager.getConnection(
    "jdbc:derby:sample;shutdown=true");

If user authentication and SQL authorization are both enabled, only the database owner can shut down the database. (See the Derby Security Guide for details on authentication and authorization.)

// shutting down an authenticated database as database owner
DriverManager.getConnection(
    "jdbc:derby:securesample;user=joeowner;password=secret;shutdown=true");

If you previously called the java.sql.DriverManager.setLoginTimeout method to enable a login timeout, a shutdown of Derby or of an individual database can fail under circumstances like the following:

• Network problems which slow down LDAP authentication
• Heavily loaded databases which take a long time time to quiesce