[JIRA-OS] Created: (CACHE-57) setCapacity does not change the maxEntries of AbstractConcurrentReadCache

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://jira.opensymphony.com/secure/ViewIssue.jspa?key=CACHE-57


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: CACHE-57
    Summary: setCapacity does not change the maxEntries of AbstractConcurrentReadCache
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: OSCache
   Versions:
             2.0 beta 2

   Assignee: Chris Miller
   Reporter: Praveen Peddi

    Created: Sat, 6 Sep 2003 1:12 PM
    Updated: Sat, 6 Sep 2003 1:12 PM

Description:
1) Instanstiate GeneralCacheAdministrator
2) The capacity is obtained from property file (lets say capacity is 1000).
3) While putting objects in the cache, debug AbstractConcurrentReadCache and notice that the maxEntries value is 1000.
4) Now call GeneralCacheAdministrator's setCapacity to set the capacity to 10000.
5) Repeat step 3 and notice that the maxExtires value is still 1000.
6) When setCapacity is called, the code has to reset the maxEntries value to the new value. Because maxEntries is the one thats used all algorithms (while removing the excess entries from cache).


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.opensymphony.com/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf