[DERBY-5316] Unload old JDBC drivers when done with them in the upgrade tests

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 10.9.1.0
• Component/s: Test
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Created: 06/Jul/11 18:51
• Updated: 24/Jul/12 17:31
• Resolved: 13/Jul/11 12:31

Description

Discussed in this thread on derby-dev: http://mail-archives.apache.org/mod_mbox/db-derby-dev/201107.mbox/[e-mail]%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.

Issue Links

• breaks: DERBY-5343 Starting 7/13/2011 weme 6.2 upgrade tests started failing with 213 failures 127 errors with java.lang.IllegalAccessException
• is related to: DERBY-4740 On Mac OSX 10.6 suites.All fails with Exception in thread "main" java.lang.OutOfMemoryError: PermGen space even with -XX:MaxPermSize=128M
• is related to: DERBY-2905 Shutting down embedded Derby does not remove all code, the AutoloadDriver is left registered in the DriverManager.
• is related to: DERBY-4895 Thread local TableDescriptor#referencedColumnMap is not removed from app threads when Derby is shut down
• is related to: DERBY-5322 Add a test to detect Classloader leaks in Derby
• is related to: DERBY-5267 Shut down engine for old versions in upgrade tests to save memory