[
https://issues.apache.org/jira/browse/DERBY-6440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13855826#comment-13855826
]
Knut Anders Hatlen commented on DERBY-6440:
-------------------------------------------
(The reason why I looked for memory leaks in the first place, was the
OutOfMemoryErrors that we've seen every now and then in the nightly testing on
JDK 8 lately (for example
[here|http://download.java.net/javadesktop/derby/request_5585930/javadb-task-3780475.html]).
I don't know if this bug is what's causing those OOMEs, though.)
> 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.0.0
> Reporter: Knut Anders Hatlen
>
> 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.1.5#6160)
