Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Mon, 11 Jul 2011 10:33:59 +0000 (UTC)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <1807528606.2582.1310380439916.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <970557658.4824.1309978336933.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (DERBY-5316) Unload old JDBC drivers when done
 with them in the upgrade tests
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Knut Anders Hatlen updated DERBY-5316:
--------------------------------------

    Attachment: deregister-v2.diff

Attaching a simplified patch (deregister-v2.diff). The v2 patch does not create a directory with the DriverUnloader class in the test directory. Instead, it creates a specialized class loader that reads it directly from the system classpath.

> Unload old JDBC drivers when done with them in the upgrade tests
> ----------------------------------------------------------------
>
>                 Key: DERBY-5316
>                 URL: https://issues.apache.org/jira/browse/DERBY-5316
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>         Attachments: deregister-v2.diff, deregister.diff
>
>
> Discussed in this thread on derby-dev: http://mail-archives.apache.org/mod_mbox/db-derby-dev/201107.mbox/%3C4E146309.3000906@gmail.com%3E
> After we're done testing an old version in the upgrade tests, its classes are still loaded in the JVM because the old driver is referenced in DriverManager. We should find a way to unload the old drivers so that the memory usage of the upgrade tests is reduced. Now we typically need to run with -XX:MaxPermSize=200M or similar options to work around this issue.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira