[
https://issues.apache.org/jira/browse/DERBY-5618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen resolved DERBY-5618.
---------------------------------------
Resolution: Duplicate
The test cases that previously were disabled because of this bug, have now been
enabled by the fix for DERBY-2162, so I'm resolving this issue as a duplicate.
The repro attached to this issue still fails, but I believe that's expected
since the URLClassLoader that references the jar file is still the context
class loader of the main thread and open after the engine shutdown. As noted in
DERBY-2162, Derby cannot close the application's class loaders at shutdown,
since it cannot tell if the application will need them again, so it has to be
the application's responsibility to close them down when they are no longer
needed.
> 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)
