[
https://issues.apache.org/jira/browse/DERBY-5316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-5316:
--------------------------------------
Attachment: deregister-check.diff
Attaching deregister-check.diff, which checks that we only had to deregister
the driver in versions known to be affected by DERBY-2905.
Committed clear-threadlocal.diff with revision 1145552.
Committed deregister-check.diff with revision 1145553.
> 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-check.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
