db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-2480) DriverManager.getConnection leaks memory when connecting to a non-existent database
Date Wed, 18 Apr 2007 21:17:15 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Bryan Pendleton resolved DERBY-2480.

       Resolution: Fixed
    Fix Version/s:
       Derby Info:   (was: [Patch Available])

Thanks Jeff for the bug report, and for the patch. Thanks John for reviewing
the change and contributing the test program. And thanks to the other
reviewers for the comments and notes.

I submitted both patches in a single change to the trunk as revision 530159.

> 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:,,,,,,,
>         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
>         Assigned To: John H. Embretsen
>            Priority: Minor
>             Fix For:
>         Attachments: d2480-junitTest_v1.diff, d2480-junitTest_v1.stat, 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.

View raw message