You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "martin stanik (JIRA)" <ji...@apache.org> on 2016/03/22 16:11:25 UTC

[jira] [Created] (DERBY-6878) unload EmbeddedDriver by using System.gc()?

martin stanik created DERBY-6878:
------------------------------------

             Summary: 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


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)