[DERBY-2480] DriverManager.getConnection leaks memory when connecting to a non-existent database

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.1.4
• Fix Version/s: 10.3.1.4
• Component/s: JDBC
• Environment: Windows Vista, JDK 1.4.2_13; Solaris 10, Sun JDK 1.4.2, 1.5.0 & 1.6.0; Red Hat Enterprise Linux 4 (2.6.9-34.ELsmp_64), Sun JDK 1.5.0 & 1.6.0
• Assignee: John Embretsen
• Reporter: Jeff Clary
• Created: 22/Mar/07 21:06
• Updated: 21/Jan/11 17:49
• Resolved: 18/Apr/07 21:16

Description

Repeated calls to java.sql.DriverManager.getConnection("jdbc:derby:C:
DOES_NOT_EXIST") leak memory and eventually lead to an OutOfMemoryError.

This bug is similar to DERBY-1947 in that ContextManager objects are not getting removed from the HashSet. The attached test program demonstrates the issue. When run with VM options -Xms8m -Xmx8m, it throws an OutOfMemoryError after 19022 calls to DriverManager.getConnection.

Issue Links

• is related to: DERBY-1947 OutOfMemoryError after repeated calls to boot and shutdown a database