Loading...

derby-dev@db.apache.org

[Prev] Thread [Next]  |  [Prev] Date [Next]

[jira] [Commented] (DERBY-2905) Shutting down embedded Derby does not remove all code, the AutoloadDriver is left registered in the DriverManager. Sebastian (Commented) (JIRA) Wed Feb 22 01:01:08 2012

    [ 
https://issues.apache.org/jira/browse/DERBY-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213466#comment-13213466
 ] 

Sebastian commented on DERBY-2905:
----------------------------------


Here my code for the shutdown:

Context ctx = new InitialContext(env);
EmbeddedConnectionPoolDataSource ds = 
(EmbeddedConnectionPoolDataSource)ctx.lookup(DB_CONTEXT);
if (ds != null) {
   ds.setShutdownDatabase("shutdown");
   ds.getConnection();
}



                
> 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
>             Fix For: 10.8.1.2
>
>         Attachments: DERBY-2905-2.diff, DERBY-2905_1.diff, DERBY-2905_3.diff, 
> DERBY-2905_part2_1.diff, DERBY-2905_part2_2.diff, DERBY-2905_part2_2_1.diff, 
> DERBY-2905_part2_2_2.diff, DERBY-2905_part2_2_3.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, 
> derby-2905-01-aa-fixAutoloadedDriverReload.diff, releaseNote.html, 
> releaseNote.html, releaseNote.html, releaseNote.html, releaseNote.html, 
> releaseNote.html, ww.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.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira