Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-5267

Shut down engine for old versions in upgrade tests to save memory

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 10.9.1.0
    • 10.9.1.0
    • Test
    • None

    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.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            knutanders Knut Anders Hatlen
            knutanders Knut Anders Hatlen
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment