You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2014/03/24 13:15:45 UTC

[jira] [Commented] (DERBY-5618) 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

    [ https://issues.apache.org/jira/browse/DERBY-5618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13944959#comment-13944959 ] 

Knut Anders Hatlen commented on DERBY-5618:
-------------------------------------------

This might be a duplicate of DERBY-2162.

> 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.1.0
>         Environment: xp professional 5.1, oracle java 6, derby 10.9 trunk
>            Reporter: Rick Hillegas
>              Labels: derby_triage10_11
>         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 was sent by Atlassian JIRA
(v6.2#6252)