[
https://issues.apache.org/jira/browse/DERBY-6878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213572#comment-15213572
]
Bryan Pendleton commented on DERBY-6878:
----------------------------------------
It seems a bit inaccurate to mark this as a duplicate of DERBY-3585,
particularly
since the removal of the incorrect GC suggestion in DERBY-3585 was a bit of
a tangent from the actual purpose of DERBY-3585.
However, it does seem that DERBY-3585 has adequately addressed this
issue, so we no longer need to leave this issue open.
> 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
>
> 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)
