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.
------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: DERBY-2162
URL: http://issues.apache.org/jira/browse/DERBY-2162
Project: Derby
Issue Type: Bug
Affects Versions: 10.2.1.6, 10.3.0.0
Reporter: Daniel John Debrunner
Assigned To: Daniel John Debrunner
Priority: Minor
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
