[ https://issues.apache.org/jira/browse/DERBY-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533120 ]
Kathey Marsden commented on DERBY-2905: --------------------------------------- On Sept 4, Dan said >I working on committing this patch. Dan, could you give us an update on your review of this issue? Are there changes needed to the patch? > 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.0.0 > Reporter: Daniel John Debrunner > Assignee: Ramin Moazeni > Attachments: DERBY-2905v0.diff, DERBY-2905v0.stat, DERBY-2905v1.diff, > DERBY-2905v1.stat, DERBY-2905v3.diff, DERBY-2905v3.stat, Main.java, > Mainv1.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.