[ 
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_2.diff

Thanks Rick. I am uploading patch DERBY_2905_part2_2.diff to change the 
reloading the engine via Class.forName(…) resulted in the AutoloadedDriver 
registered. This patch also provide the deregister attribute. The default 
behavior for shutdown=true is to set deregister=true. AutoloadedDriver will not 
be in DriverManager. If users set deregister=false, the AutoloadDriver will not 
be deregister from DriverManager. The AutoloadTest create test cases like: 
default shutdown behavior, deregister=true, deregister=false and also wrong 
name of deregister attribute. The patch is ready for review. 
Suites.all and derby passed before fixing the reload engine resulted in 
AutoloadedDriver begin registered. I will run the tests again.



> 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-2905_part2_2.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, 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to