[
https://issues.apache.org/jira/browse/DERBY-5618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217194#comment-13217194
]
Rick Hillegas commented on DERBY-5618:
--------------------------------------
Hi Mike,
I also am not an expert on accessing databases via the classpath subprotocol.
However, the Developer's Guide says this in the section titled "Accessing
databases from the classpath":
"In most cases, you access databases from the file system. However, it is also
possible to access databases from the classpath. The databases can be archived
into a jar or zip file or left as is.
All such databases are read-only.
To access an unarchived database from the classpath, specify the name of the
database relative to the directory in the classpath. You can use the classpath
subprotocol if such a database is ambiguous within the directory system."
> On Windows, orderly engine shutdown does not release the file handle on a jar
> file containing a database which was booted using the classpath subprotocol
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5618
> URL: https://issues.apache.org/jira/browse/DERBY-5618
> Project: Derby
> Issue Type: Bug
> Components: Services, Store
> Affects Versions: 10.9.0.0
> Environment: xp professional 5.1, oracle java 6, derby 10.9 trunk
> Reporter: Rick Hillegas
> Labels: derby_triage10_9
> Attachments: 5618.sql, FileUtils.java
>
>
> Boot a database in a jar file, using the classpath subprotocol, then shutdown
> the engine. This leaves the jar file still open on Windows. However, orderly
> engine shutdown correctly releases the file if you boot it using the jar
> subprotocol instead. I will attach a repro.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
