Bug 13142 - HashMapObjectCache grows beyond its maxSize
Summary: HashMapObjectCache grows beyond its maxSize
Status: RESOLVED WONTFIX
Alias: None
Product: Slide
Classification: Unclassified
Component: Core (show other bugs)
Version: 1.0.11
Hardware: All All
: P3 major (vote)
Target Milestone: ---
Assignee: Slide Developer List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-09-30 15:20 UTC by Lukasz Kowalczyk
Modified: 2004-11-16 19:05 UTC (History)
0 users


Attachments
Alternative Implementation for ObjectCache (3.95 KB, text/plain)
2003-05-26 14:14 UTC, Martin Holz 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lukasz Kowalczyk 2002-09-30 15:20:20 UTC 
The class org.apache.slide.util.HashMapObjectCache doesn't respect its maxSize 
parameter. An easy fix would be to add cache size checking in the put() method.
Comment 1 Martin Holz 2003-05-26 14:14:14 UTC 
Created attachment 6495 [details]
Alternative Implementation for ObjectCache
Comment 2 Martin Holz 2003-05-26 14:19:13 UTC 
Under some circumstances, HashMapObjectCache does not cache at all. Replacing
HashMapObjectCache with LRUObjectCache can increase performance of Propfind
15 times or more. LRUObjectCache is a very thin wrapper around 
jakarata-commons-collections LRUMap.
Comment 3 Martin Holz 2004-02-01 17:14:19 UTC 
I have deprecated HashMapObjectCache, since it is not longer used.