You can also configure your system to automatically boot all databases
in the system when it starts up; see "derby.system.bootAll" in the . Because of the time needed
to boot a database, the number of databases in the system directory affects
startup performance if you use that configuration.
Once a database has been booted within a system,
it remains active until the system
has been shut down or until you shut down the database individually.
When boots a database,
a message is added to the log file. The message includes the
version that the
database was booted with, along with information about the Java version,
the user's working directory, and the location of the
system directory, if
the user specified it using the derby.system.home property. If
derby.system.home was not specified, its value is reported as null, as in
the following example:
Thu Sep 13 09:52:15 EDT 2012:
Booting Derby version The Apache Software Foundation - Apache Derby
- 10.10.0.0 - (1384314): instance a816c00e-0139-bfe6-bff8-000000a155b8
on database directory C:\sampledb with class loader
sun.misc.Launcher$AppClassLoader@9931f5
Loaded from file:C:\db-derby-10.10.0.0-bin\lib\derby.jar
java.vendor=Oracle Corporation
java.runtime.version=1.7.0_07-b11
user.dir=C:\
os.name=Windows XP
os.arch=x86
os.version=5.1
derby.system.home=null
Database Class Loader started - derby.database.classpath=''
The number of databases running in a system
is limited only by the amount of memory available in the JVM.