db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DERBY-5267) Shut down engine for old versions in upgrade tests to save memory
Date Tue, 14 Jun 2011 09:28:47 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen resolved DERBY-5267.
---------------------------------------

          Resolution: Fixed
       Fix Version/s: 10.9.0.0
    Issue & fix info:   (was: [Patch Available])

Committed revision 1135432.

> 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
>             Fix For: 10.9.0.0
>
>         Attachments: shutdown-engine.diff
>
>
> 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

        

Mime
View raw message