Shut down engine for old versions in upgrade tests to save memory
-----------------------------------------------------------------
Key: DERBY-5267
URL: https://issues.apache.org/jira/browse/DERBY-5267
Project: Derby
Issue Type: Improvement
Components: Test
Affects Versions: 10.9.0.0
Reporter: Knut Anders Hatlen
Assignee: Knut Anders Hatlen
Priority: Minor
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
