db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-538) Investigate using the standard java.net.URLClassLoader for database class loading.
Date Thu, 07 Dec 2006 00:21:22 GMT
    [ http://issues.apache.org/jira/browse/DERBY-538?page=comments#action_12456267 ] 
Daniel John Debrunner commented on DERBY-538:

Java bug 4950148 means that the closing of the jar file opened by URClassLoader is delayed
until that object's GC, which can cause issues for tests which try to cleanup after a database


Seem to hit this bug if I use this class loader, also seen in DatabaseClassLoadingTest for
the testDatabaseInClasspath() which uses URLClassLoader. Once the test is complete and the
database shutdown, the jar file cannot be removed from the file system on windows. Need to
inviestigate more as to what is going on.

> Investigate using the standard java.net.URLClassLoader for database class loading.
> ----------------------------------------------------------------------------------
>                 Key: DERBY-538
>                 URL: http://issues.apache.org/jira/browse/DERBY-538
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Services
>            Reporter: Daniel John Debrunner
>         Assigned To: Daniel John Debrunner
> Would change the fix for DERBY-537) so that's why it is a sub-task.
> Use of the standard class loader would reduce security concerns and allow jars stored
in the database to take advantage of standard features such as package sealing.

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


View raw message