Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
10.9.1.0
-
None
-
None
-
High Value Fix
Description
It would be good to have a test that detects class loader leaks in Derby. This problem sometimes shows up indirectly by the requirement for extra Permgen space with some jvm's running the upgrade test, but moving forward it would be good to have a specific functional test for this. Perhaps a test could be added to the lowmem suite that iteratively boots and shutdown's Derby in new URL Classloaders and ensures we do not run out of memory. In the IBM JVM the classes are loaded in the heap, so just a low heap should pop any problem. For the Oracle JVM we could probably make enough iterations that a leak would cause a Permgen OOM. If this does not work, Kristian mentioned in DERBY-5316 that perhaps tracing the unloading of classes could be used.
Attachments
Issue Links
- relates to
-
DERBY-5316 Unload old JDBC drivers when done with them in the upgrade tests
- Closed