[
https://issues.apache.org/jira/browse/DERBY-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486479
]
Bryan Pendleton commented on DERBY-2480:
----------------------------------------
Jeff, I believe you should assign the bug to *yourself*, since you are the one
who developed the fix.
I see that your patch includes a code change only. Is there a way to construct
a test case which
demonstrates the bug and the fix? John, I see that you worked with the repro
code; do you think we
can extract a test case from the repro code?
> DriverManager.getConnection leaks memory when connecting to a non-existent
> database
> -----------------------------------------------------------------------------------
>
> Key: DERBY-2480
> URL: https://issues.apache.org/jira/browse/DERBY-2480
> Project: Derby
> Issue Type: Bug
> Affects Versions: 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.0.0
> 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
> Reporter: Jeff Clary
> Priority: Minor
> Attachments: DERBY-2480-1.diff, derbyall_report.txt,
> heap-server-Xmx32m.png, Patch_DERBY-1947_and_DERBY-2480.diff,
> testOpenOfMissingDatabase.java
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
