db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-4646) Implement dual boot protection on CDC Foundation 1.1/phoneME platform for non-Windows platforms.
Date Thu, 06 May 2010 22:17:48 GMT
Implement dual boot protection on CDC Foundation 1.1/phoneME platform for non-Windows platforms.
------------------------------------------------------------------------------------------------

                 Key: DERBY-4646
                 URL: https://issues.apache.org/jira/browse/DERBY-4646
             Project: Derby
          Issue Type: Improvement
          Components: Store
    Affects Versions: 10.5.3.0, 10.5.2.0, 10.5.1.1, 10.4.2.0, 10.4.1.3, 10.3.3.0, 10.3.2.1,
10.3.1.4, 10.2.2.0, 10.2.1.6, 10.1.3.1, 10.1.2.1, 10.1.1.0, 10.0.2.1, 10.0.2.0
         Environment: Linux; Sun CVM phoneme_advanced_mr2
            Reporter: Dag H. Wanvik


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.

Cf discussion in 
https://issues.apache.org/jira/browse/DERBY-4179?focusedCommentId=12864945&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12864945

Apparently this is not an issue on the Windows platform.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message