You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2007/10/04 01:47:51 UTC
[jira] Created: (DERBY-3102) Statements are not removed from the
cache, even when they are of no use, e.g. statements that reference a
dropped table.
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
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.
[jira] Commented: (DERBY-3102) Statements are not removed from the
cache, even when they are of no use, e.g. statements that reference a
dropped table.
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532297 ]
Daniel John Debrunner commented on DERBY-3102:
----------------------------------------------
Is this a bug or an improvement?
I would say improvement as no incorrect behaviour occurs to due the plans being left in the cache.
If it's a bug then I would say it's minor, not 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.
[jira] Commented: (DERBY-3102) Statements are not removed from the
cache, even when they are of no use, e.g. statements that reference a
dropped table.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DERBY-3102) Statements are not removed from the
cache, even when they are of no use, e.g. statements that reference a
dropped table.
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532309 ]
Daniel John Debrunner commented on DERBY-3102:
----------------------------------------------
I don't think there is a resource leak, the cache will fill up with statements and then statements will be replaced.
Thus there should be no running out of memory. I think if you continued the test runs you would see the cache size top out at 100.
> 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.
[jira] Updated: (DERBY-3102) Statements are not removed from the
cache, even when they are of no use, e.g. statements that reference a
dropped table.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-3102:
----------------------------------
Attachment: TestCache.java
> 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.
[jira] Updated: (DERBY-3102) Statements are not removed from the
cache, even when they are of no use, e.g. statements that reference a
dropped table.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-3102:
----------------------------------
Priority: Minor (was: Major)
Issue Type: Improvement (was: Bug)
I changed this to be a minor improvement. I misinterpreted the comment in DERBY-2344 to indicate that this might be the root cause of the DERBY-2344 failure. From Dan's comment in this issue I think it is an unlikely source of the problem. Thanks Dan for the clarification.
> 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: Improvement
> Components: SQL
> Affects Versions: 10.3.1.4
> Reporter: Kathey Marsden
> Priority: Minor
> 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.