[DERBY-4125] The in-memory storage back end doesn't work on Windows

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 10.6.1.0
• Fix Version/s: 10.5.1.1, 10.6.1.0
• Component/s: Store
• Assignee: Kristian Waagan
• Reporter: Kristian Waagan
• Created: 27/Mar/09 09:00
• Updated: 09/Jun/09 09:37
• Resolved: 31/Mar/09 10:18

Description

Bug reported by Knut Magne Solem, see DERBY-646.

Using the in-memory storage back end fails on Windows (i.e. connect 'jdbc:derby:memory:MyDbTest;create=true'; from ij):
ERROR XJ001: Java exception: 'ASSERT FAILED serviceName = memory:C:\Documents and Settings\user\workspace\derby\MyDbTest;storageFactory.getCanonicalName() = C:\Documents and Settings\user\workspace\derby\MyDbTest: org.apache.derby.shared.common.sanity.AssertFailure'.

With an insane build, the error messages will look like this:
ERROR XJ041: Failed to create database 'memory:myDB', see the next exception for details.
ERROR XBM01: Startup failed due to an exception. See next exception for details.
ERROR XSTB2: Cannot log transaction changes, maybe trying to write to a read only database.

The error occurs during boot, which means Windows users are unable to use the in-memory back end at all.