Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <14506850.1157112143353.JavaMail.jira@brutus>
Date: Fri, 1 Sep 2006 05:02:23 -0700 (PDT)
From: "Knut Anders Hatlen (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Closed: (DERBY-1142) Metadata calls leak memory
In-Reply-To: <1004750107.1143053645464.JavaMail.jira@ajax>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-1142?page=all ]

Knut Anders Hatlen closed DERBY-1142.
-------------------------------------

    Fix Version/s: 10.2.1.0
       Resolution: Fixed

Verified that the fix for DERBY-418 also fixes the remaining problems for this issue.

> Metadata calls leak memory
> --------------------------
>
>                 Key: DERBY-1142
>                 URL: http://issues.apache.org/jira/browse/DERBY-1142
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.1.2.1, 10.2.1.0
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>             Fix For: 10.2.1.0
>
>         Attachments: 1142_close_single_use_activations_draft.txt, metadataloop.java
>
>
> When calling a DatabaseMetaData method that returns a ResultSet,
> memory is leaked. A loop like this (using the embedded driver)
>   while (true) {
>     ResultSet rs = dmd.getSchemas();
>     rs.close();
>   }
> will eventually cause an OutOfMemoryError.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira