[DERBY-2905] Shutting down embedded Derby does not remove all code, the AutoloadDriver is left registered in the DriverManager.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.2.2.0, 10.3.1.4, 10.4.1.3
• Fix Version/s: 10.8.1.2
• Component/s: JDBC
• Urgency: Normal
• Issue & fix info: High Value Fix
• Bug behavior facts: Regression
• Assignee: Lily Wei
• Reporter: Daniel John Debrunner
• Created: 05/Jul/07 22:31
• Updated: 03/Sep/14 08:31
• Resolved: 15/Feb/11 20:51

Description

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.

Issue Links

• incorporates: DERBY-5085 After specifying deregister=false on the engine shutdown URL, Derby forgets that the default behavior is deregister=true
• is related to: DERBY-6224 Issues with latest JDK 8 EA build because of missing SQLPermission
• relates to: DERBY-5316 Unload old JDBC drivers when done with them in the upgrade tests