[
https://issues.apache.org/jira/browse/DERBY-5316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060807#comment-13060807
]
Kathey Marsden commented on DERBY-5316:
---------------------------------------
Actually, I had hoped t that Lily's work on DERBY-2905 would resolve this
issue, but it seems like it is still really hard to get Derby unloaded once
loaded in a class loader. As it is more and more common to see users use
custom class loaders, we should also document the appropriate way to not only
shutdown but unload Derby when using class loaders.
> Unload old JDBC drivers when done with them in the upgrade tests
> ----------------------------------------------------------------
>
> Key: DERBY-5316
> URL: https://issues.apache.org/jira/browse/DERBY-5316
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Reporter: Knut Anders Hatlen
>
> Discussed in this thread on derby-dev:
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/201107.mbox/%[email protected]%3E
> After we're done testing an old version in the upgrade tests, its classes are
> still loaded in the JVM because the old driver is referenced in
> DriverManager. We should find a way to unload the old drivers so that the
> memory usage of the upgrade tests is reduced. Now we typically need to run
> with -XX:MaxPermSize=200M or similar options to work around this issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
