[
https://issues.apache.org/jira/browse/DERBY-5316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063489#comment-13063489
]
Knut Anders Hatlen commented on DERBY-5316:
-------------------------------------------
We don't actually call deregisterDriver() on the versions that already
deregister the driver as part of the shutdown, since DriverManager.getDrivers()
will return an empty Enumeration for those versions. But you were perhaps
thinking that we should skip the entire process of checking whether there are
any drivers registered? Or perhaps have an assert to verify that the driver in
fact has been deregistered?
> 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
> Assignee: Knut Anders Hatlen
> Attachments: clear-threadlocal.diff, deregister-v2.diff,
> deregister.diff
>
>
> 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
