[ http://issues.apache.org/jira/browse/DERBY-1838?page=comments#action_12435968 ] Suresh Thalamati commented on DERBY-1838: -----------------------------------------
you are right John. Dual boot through multiple JVMs is prevented on Unix from JDK1.4 (1.4.0) using the file lock support., provided in jdk1.4. /suresh > Derby allows dual boot which can cause corruption of databases with JVM's > lower than 1.4.2 on non-windows systems > ------------------------------------------------------------------------------------------------------------------ > > Key: DERBY-1838 > URL: http://issues.apache.org/jira/browse/DERBY-1838 > Project: Derby > Issue Type: Bug > Components: Store > Affects Versions: 10.0.2.0, 10.0.2.1, 10.0.2.2, 10.1.1.0, 10.2.1.0, > 10.1.2.1, 10.1.3.0, 10.3.0.0, 10.1.4.0, 10.1.3.1, 10.1.3.2, 10.2.2.0 > Reporter: Kathey Marsden > Priority: Critical > > On non-windows systems accidental access of a database from two JVM's is not > prevented on JVM's lower than 1.4.2. The issue can be triggered by a > common user error, for example accessing a database from two ij sessions. > This can cause unrecoverable corruption. It is critical that users upgrade > to 1.4.2 if there is a possibility that a user might access Derby in this way. > There was no known way to fix this issue until 1.4.2, so it is not likely > that it can be resolved within Derby. Upgrade of the JVM is the only known > solution now. > Note: Even with 1.4.2 the dual boot issue exists in certain scenarios which > are not well documented. DERBY-700 has been filed and hopefully other fatal > usage cases that can lead to dual boot can be isolated and resolved. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
