No lock file thread

.NET: Db4oFactory.Configure().LockDatabaseFile(false)

Advantage

will prevent the creation of a lock file thread on Java platforms without NIO (< JDK 1.4.1).

Effect

If file locking is not available on the system, db4o will regularily write a timestamp lock information to the database file, to prevent other VM sessions from accessing the database file at the same time. Uncontrolled concurrent access would inevitably lead to corruption of the database file. If the application ensures that it can not be started multiple times against the database file, db4o file locking may not be necessary.

Alternate Strategies

Database files can safely be opened from multiple sessions in readonly mode. Use:

.NET: Db4oFactory.Configure().ReadOnly(true)