Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Tue, 1 Feb 2011 00:35:28 +0000 (UTC)
From: "Lily Wei (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <1486294591.1073.1296520528991.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Updated: (DERBY-2905) Shutting down embedded Derby does not
 remove all code, the AutoloadDriver is left registered in the
 DriverManager.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Lily Wei updated DERBY-2905:
----------------------------

    Attachment: DERBY-2905_part2_1.diff

The DERBY-2905_part2_1.diff patch adds the attribute deregistere. The default behavior on shutdown is to deregister AutoloaderDriver. If users specify deregister=false attribute at shutdown, Derby will not deregister AutoloadedDriver. And, getConnection will get a new connection. I still need to write releaseNote.html for this issue.

I had run more tests on the side. I am still in the middle of getting them into AutoloadTest. The code is ready for review especially on adding new error message part. I am not sure we should add new error message here. Any suggestion is welcome.

Running suites.all and derbyall now.

> Shutting down embedded Derby does not remove all code, the AutoloadDriver is left registered in the DriverManager.
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2905
>                 URL: https://issues.apache.org/jira/browse/DERBY-2905
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.2.2.0, 10.3.1.4, 10.4.1.3
>            Reporter: Daniel John Debrunner
>            Assignee: Lily Wei
>         Attachments: DERBY-2905-2.diff, DERBY-2905_1.diff, DERBY-2905_3.diff, DERBY-2905_part2_1.diff, DERBY-2905v0.diff, DERBY-2905v0.stat, DERBY-2905v1.diff, DERBY-2905v1.stat, DERBY-2905v3.diff, DERBY-2905v3.stat, Main.java, Mainv1.java, Repro2905.java
>
>
> After a shutdown of the embedded driver the AutoloadDriver is not unregistered from DriverManager. However it does not support any future loading of connections so it has no value in remaining registered. Since the DriverManager class will remain forever, this means the Derby code will remain forever in the JVM, even if Derby was loaded by a separate class loader.
> Regression from 10.1 since before the AutoloadedDriver the internal driver did unregister itself from the DriverManager on a shutdown.

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