[
https://issues.apache.org/jira/browse/DERBY-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan closed DERBY-4125.
----------------------------------
> The in-memory storage back end doesn't work on Windows
> ------------------------------------------------------
>
> Key: DERBY-4125
> URL: https://issues.apache.org/jira/browse/DERBY-4125
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.6.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Critical
> Fix For: 10.5.1.1, 10.6.0.0
>
> Attachments: derby-4125-1a-improved_path_handling.diff
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
