db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Assigned: (DERBY-1142) Metadata calls leak memory
Date Tue, 18 Jul 2006 21:59:15 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1142?page=all ]

Daniel John Debrunner reassigned DERBY-1142:
--------------------------------------------

    Assignee:     (was: Daniel John Debrunner)

Since this is an extreme edge case now, I'm no longer working on it.

> 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.0.0
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>         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

        

Mime
View raw message