You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Phil Steitz (Closed) (JIRA)" <ji...@apache.org> on 2011/12/01 08:01:41 UTC

[jira] [Closed] (DBCP-371) DelegatingDatabaseMetaData

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

Phil Steitz closed DBCP-371.
----------------------------

       Resolution: Duplicate
    Fix Version/s:     (was: 1.2)
                   1.4.1

This duplicates DBCP-330, which has been fixed in the DBCP_1_4 branch.  The fix will be included in DBCP 1.3.1 / 1.4.1
                
> DelegatingDatabaseMetaData
> --------------------------
>
>                 Key: DBCP-371
>                 URL: https://issues.apache.org/jira/browse/DBCP-371
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.3, 1.4
>         Environment: Informix database
>            Reporter: Fredrik Bertilsson
>            Priority: Critical
>             Fix For: 1.4.1
>
>
> When calling Connection.getMetaData() new objects of DelegationDatabaseMetaData and corresponding vendor specific objects (like IfxDatabaseMetaData) are created and never released for garabage collection. This bug seem to have been introduced in version 1.3. Version 1.2 does not have this problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira