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] Commented: (DERBY-1142) Metadata calls leak memory
Date Thu, 23 Mar 2006 17:44:20 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1142?page=comments#action_12371598 ] 

Daniel John Debrunner commented on DERBY-1142:

May be unrelated but part of my example patch for DERBY-872 I had a feeling was a more generic
issue about activations not being closed correctly in some situations, though I think it may
have only been related to single use activations. It's on  my list to extract that code and
see if it made sense by itself and passed derbyall. 

> Metadata calls leak memory
> --------------------------
>          Key: DERBY-1142
>          URL: http://issues.apache.org/jira/browse/DERBY-1142
>      Project: Derby
>         Type: Bug
>   Components: JDBC
>     Versions:,
>     Reporter: Knut Anders Hatlen
>     Priority: Minor
>  Attachments: 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:
For more information on JIRA, see:

View raw message