[DERBY-5618] On Windows, orderly engine shutdown does not release the file handle on a jar file containing a database which was booted using the classpath subprotocol

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 10.9.1.0
• Component/s: Services, Store
• Labels: derby_triage10_11
• Environment: xp professional 5.1, oracle java 6, derby 10.9 trunk
• Urgency: Normal
• Issue & fix info: High Value Fix, Repro attached
• Assignee: Unassigned
• Reporter: Richard N. Hillegas
• Created: 15/Feb/12 14:18
• Updated: 21/Jan/15 00:23
• Resolved: 27/Mar/14 08:55

Description

Boot a database in a jar file, using the classpath subprotocol, then shutdown the engine. This leaves the jar file still open on Windows. However, orderly engine shutdown correctly releases the file if you boot it using the jar subprotocol instead. I will attach a repro.

Issue Links

• duplicates: DERBY-2162 Shutting down a database loaded from a jar file via the classpath and URLClassLoader leaves an open file reference to the jar file containing the database.
• relates to: DERBY-866 Derby User Management Enhancements