[
https://issues.apache.org/jira/browse/DERBY-5618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208553#comment-13208553
]
Rick Hillegas commented on DERBY-5618:
--------------------------------------
Hi Kristian,
That is a good point. The file handle is probably still open on *nix platforms
too. It's just that we notice the orphaned file handle on Windows. Note that in
the repro, the same process runs the engine, shuts it down, and then tries to
delete the jar file. Thanks.
> 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
> 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
