Cloudscape Properties
Page 11 of 47

cloudscape.database.forceDatabaseLock

Function

On some platforms, if set to true, prevents Cloudscape from booting a database if a db.lck is present.

Cloudscape attempts to prevent two JVMs from accessing a database at one time (and potentially corrupting it) with the use of a file called db.lck in the database directory. On some operating systems, the use of a lock file does not guarantee single access, and so Cloudscape only issues a warning and may allow multiple JVM access even when the file is present. (For more information, see Double-Booting System Behavior in the Cloudscape Developer's Guide.)

Cloudscape provides the property cloudscape.database.forceDatabaseLock for use on platforms that do not provide the ability for Cloudscape to guarantee single JVM access. By default, this property is set to false. When this property is set to true, if Cloudscape finds the db.lck file when it attempts to boot the database, it throws an exception and does not boot the database.

NOTE: This situation can occur even when no other JVMs are accessing the database; in that case, remove the db.lck file by hand in order to boot the database. If the db.lck file is removed by hand while a JVM is still accessing a Cloudscape database, there is no way for Cloudscape to prevent a second VM from starting up and possibly corrupting the database. In this situation no warning message is logged to the error log.

Default

false

Example

cloudscape.database.forceDatabaseLock=true

Scope

system-wide

Dynamic or Static

This property is static; if you change it while Cloudscape is running, the change does not take effect until you reboot.