[
https://issues.apache.org/jira/browse/DERBY-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532299
]
Kathey Marsden commented on DERBY-3102:
---------------------------------------
I think it is a bug because it creates a resource leak even when the
application cleans up normally. If it is what causes the long running
applications like the test runs to run out of memory, I think it is major.
> Statements are not removed from the cache, even when they are of no use, e.g.
> statements that reference a dropped table.
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3102
> URL: https://issues.apache.org/jira/browse/DERBY-3102
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.3.1.4
> Reporter: Kathey Marsden
> Attachments: TestCache.java
>
>
> Dan pointed this out in DERBY-2344 and I thought it worthy of its own bug.
> The attached program shows the number of statements in the cache growing even
> though the table is dropped.
> [C:/kmarsden/repro/DERBY-2344] java TestCache
> number of cache entries: 5
> number of cache entries: 9
> number of cache entries: 13
> number of cache entries: 17
> number of cache entries: 21
> number of cache entries: 25
> number of cache entries: 29
> number of cache entries: 33
> number of cache entries: 37
> number of cache entries: 41
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
