[DERBY-5267] Shut down engine for old versions in upgrade tests to save memory

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.9.1.0
• Fix Version/s: 10.9.1.0
• Component/s: Test
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Created: 09/Jun/11 14:39
• Updated: 06/Jul/11 18:52
• Resolved: 14/Jun/11 09:27

Description

The memory requirements for the upgrade tests seem to go up each time we add a new release. Lately, they've started failing on phoneME with the error message saying "Number of class names exceeds vm limit." It looks to me as if the problem is that we don't shut down the engine when we've finished testing a version, so we eventually end up with 19 different versions of the engine loaded in the same process. I think it would be good to shut down the old engines when we're done with them to free up resources.

Issue Links

• relates to: DERBY-5316 Unload old JDBC drivers when done with them in the upgrade tests