[DERBY-2162] Shutting down a database loaded from a jar file via the classpath and URLClassLoader leaves an open file reference to the jar file containing the database.

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.2.1.6, 10.3.1.4
• Fix Version/s: 10.11.1.1
• Component/s: Test
• Labels: derby_triage10_5_2
• Urgency: Normal
• Assignee: Knut Anders Hatlen
• Reporter: Daniel John Debrunner
• Created: 07/Dec/06 21:30
• Updated: 21/Jan/15 03:23
• Resolved: 27/Mar/14 12:40

Description

A bug in java.net.URLClassLoader causes the underlying jar file to be held open once a resource has been fetched and opened.
Loading a class or just accessing the URL for the resource does not keep the jar open. Reported the bug to Sun, it is similar to the existing bug Java bug 4950148 but in this case no amount of garbage collection will close the jar.

Derby exposes this as all containers/files are opened using as resources when loading the database from the classpath.

On windows this is seen as the inability to delete the jar file, seen by the fixture testDatabaseInClasspath in DatabaseClassLoadingTest.

Similar to DERBY-2083 but due to a different cause.

Issue Links

• is duplicated by: 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