db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DERBY-6878) unload EmbeddedDriver by using System.gc()?
Date Sun, 27 Mar 2016 18:56:25 GMT

     [ https://issues.apache.org/jira/browse/DERBY-6878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bryan Pendleton resolved DERBY-6878.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 10.5.1.1

Marked as fixed by subversion revision 644555


> unload EmbeddedDriver by using System.gc()?
> -------------------------------------------
>
>                 Key: DERBY-6878
>                 URL: https://issues.apache.org/jira/browse/DERBY-6878
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: martin stanik
>            Priority: Minor
>              Labels: easyfix
>             Fix For: 10.5.1.1
>
>
> derby development doc suggests one can 'unload driver class':
> > You cannot explicitly request that the JVM unload a class, but you can ensure that
the EmbeddedDriver class is unloaded by using a System.gc() ....
> this advice is unfortunate, because:
> 1. it is wrong - one can not unload single class. 
>     only whole classloader with all it's classes might be unloaded (this needs be organized
ahead)
> 2. one may get false impression unloading driver is good practice/desirable/necessary.
>     i believe it is not.
> i suggest to remove the advice unless there is provided a scenario when unloading driver
is needed +  explanation how to do it properly (derby driver needs be loaded into extra classloader).
>     



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message