[ https://issues.apache.org/jira/browse/DERBY-5316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13061165#comment-13061165
]
Knut Anders Hatlen commented on DERBY-5316:
-------------------------------------------
I instrumented the DriverManager.registerDriver() and DriverManager.unregisterDriver() and
ran the upgrade tests. It looks like the combination of DERBY-2905 and DERBY-5267 made the
upgrade tests deregister driver versions lower than 10.2 and higher than 10.7. But we still
have 11 versions that don't get 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
>
> Discussed in this thread on derby-dev: http://mail-archives.apache.org/mod_mbox/db-derby-dev/201107.mbox/%3C4E146309.3000906@gmail.com%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
|