Bug reported by Knut Magne Solem, see
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.