[ http://issues.apache.org/jira/browse/DERBY-1142?page=comments#action_12371700 ]
Knut Anders Hatlen commented on DERBY-1142:
-------------------------------------------
My proposed solution actually fixed the memory leak, but broke
derbyall. These tests failed:
derbyall/derbyall.fail:jdbcapi/odbc_metadata.java
derbyall/derbyall.fail:jdbcapi/bestrowidentifier.sql
derbyall/derbynetmats/derbynetmats.fail:jdbcapi/bestrowidentifier.sql
derbyall/derbynetclientmats/derbynetmats.fail:jdbcapi/bestrowidentifier.sql
> Metadata calls leak memory
> --------------------------
>
> Key: DERBY-1142
> URL: http://issues.apache.org/jira/browse/DERBY-1142
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.1.2.1, 10.2.0.0
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|