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

Lily Wei commented on DERBY-2905:
---------------------------------

+1 on communicating more in turn of conflicts and potential fix. I will be more 
than happy to keep working on resolving getParentLogger issue for 
AutoloadedDriver. I will definitely appreciate Rick's suggestion for how to 
proceed.
As far as I can see, we need to create AutoloadedDriver40 in 
AutoloadedDriver.registerDriverModule. Something like this:
           if (_autoloadedDriver == null) {
                //Support JDBC 4 or higher (DERBY-2905)
                if (HAVE_DRIVER && HAVE_SQLXML) {
                    AutoloadedDriver40.reloadAutoloadedDriver40();
                }
However, I am having compiler error on the line 
"AutoloadedDriver40.reloadAutoloadedDriver40 on reflect, invoke etc.


> 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-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, 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