[DERBY-1838] Derby allows dual boot which can cause corruption of databases with JVM's lower than 1.4.2 on non-windows systems

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Won't Fix
• Affects Version/s: 10.0.2.0, 10.0.2.1, 10.0.2.2, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.1.3.2, 10.1.3.3, 10.2.1.6, 10.2.2.0, 10.3.1.4
• Component/s: Store
• Urgency: Low
• Assignee: Unassigned
• Reporter: Katherine Marsden
• Created: 11/Sep/06 17:58
• Updated: 05/Jul/10 17:32
• Resolved: 22/Mar/07 14:21

Description

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.