Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.1.4, 10.3.2.1, 10.3.3.0, 10.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0
-
None
-
None
-
Linux; Sun CVM phoneme_advanced_mr2
Description
The small device platform we support based on CDC/Foundation 1.1 does not support the NIO based method used by Derby to guarantee against dual boots of a database by different VMs. It would be nice to have a way to guarantee against this scenario.
Currently, one would have to use the property derby.database.forceDatabaseLock with the ensuing hassle of cleaning away orphaned lock files.
The default behavior is "false", so then all Derby does if to print a warning to derby.log and System.err.
Apparently this is not an issue on the Windows platform.
Attachments
Issue Links
- is related to
-
DERBY-700 Derby does not prevent dual boot of database from different classloaders on Linux and Mac OS X
- Closed
-
DERBY-4179 bootLock.java fails with missing exception on z/OS with pmz3160sr2ifix-20081021_01(SR2+IZ32776+IZ33456), and Windows Vista
- Closed