[
https://issues.apache.org/jira/browse/DERBY-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lily Wei updated DERBY-2905:
----------------------------
Attachment: Repro2905.java
DERBY-2905_1.diff
Hi Rick:
Thank you so much for the prompt response and leading me to the ideal
solution we would like to have - satisfied users who would like to have the
10.1 behavior and users who would like to have the autoloading behavior.
Judging from the timeframe of the discussion, this is not an easy problem to
get agreement upon. I have to admit I don't totally understand all the
complication so any health debate is welcome with the modify solution inspire
by Ramin and Dan. The DERBY-2905-1.diff is the proposal patch and
Repro2905.java is to show Derby behavior before and after this patch.
I found this solution solve the following issues
1. Unload Derby classes after engine shutdown.
2. Preserve 10.1 behavior and support any future loading of connections
Disadvantage: It does not preserve the autoloading idiom.
I am proposing Derby allows support any future loading of connections.
I did not testing the impact of performance for this patch. Suites.all runs
clean.
Any proposal solution is welcome. Thanks!!!
> 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
> Attachments: DERBY-2905_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.
-
You can reply to this email to add a comment to the issue online.
