[jira] [Resolved] (DERBY-6440) Connections opened by ForeignTableVTI never get released

["Mike Matrigali (JIRA)" <ji...@apache.org>]

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

Mike Matrigali resolved DERBY-6440.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 10.10.2.1
         Assignee: Rick Hillegas  (was: Mike Matrigali)

backported to 10.10 and resolving.  resetting original owner.  Do not plan on additional backport of this issue at this time.

> Connections opened by ForeignTableVTI never get released
> --------------------------------------------------------
>
>                 Key: DERBY-6440
>                 URL: https://issues.apache.org/jira/browse/DERBY-6440
>             Project: Derby
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 10.11.1.1
>            Reporter: Knut Anders Hatlen
>            Assignee: Rick Hillegas
>             Fix For: 10.10.2.1, 10.11.1.1
>
>         Attachments: derby-6440-01-aa-dropConnectionOnUnload.diff
>
>
> I noticed during a run of suites.All that one database instance never got garbage collected, even after it had been shut down. It turned out it could not get garbage collected because it was still referenced from the static HashMap _connections in ForeignTableVTI. Looking closer at ForeignTableVTI, it looks as if it only calls put() and get() on the HashMap, never remove(), so its memory footprint will keep increasing as it is used.
> It would be good to have some way (preferably automatic) of releasing the resources held by ForeignTableVTI when they are no longer needed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)