[
https://issues.apache.org/jira/browse/DERBY-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993638#comment-12993638
]
Kathey Marsden commented on DERBY-2905:
---------------------------------------
What user functionality is broken with the DERBY_2905_part2_2.diff? I have
not seen any failures on JDK 1.6. Is it JDK 1.7 specific related functionality
of getParentLogger when the AutoloadedDriver is reloaded after shutdown?
Since there is no regression to previous releases and no JDK 1.7 released. I
think it would make sense to file a separate issue for the JDK 1.7 issue and
work on that separately as part of the JDBC 4.1 work.
I think in general the Autoloader code was designed with the assumption that it
would never be unloaded with all the references in DataSources and such, so it
was quite tricky I think for Lily to figure out how to get the updates in all
the right places, but it does work and is a great improvement over the current
state. Maybe the addition of AutoloadedDriver40 warrants a refactoring to
remove that assumption.
> 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
