[jboss-jira] [JBoss JIRA] Updated: (JBVFS-134) IterableTimedVFSCache doesn't cache entries once they get expired

[Ales Justin (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBVFS-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ales Justin updated JBVFS-134:
------------------------------

    Attachment: jboss-vfs.jar


I changed the peek to get,
and added proper invalidation code.

Can you try the attached jar and let me know if this works for you?
If yes, I'll do a proper VFS 2.2.0.Alpha3 release.
If no, I'll keep investigating.

> IterableTimedVFSCache doesn't cache entries once they get expired
> -----------------------------------------------------------------
>
>                 Key: JBVFS-134
>                 URL: https://jira.jboss.org/jira/browse/JBVFS-134
>             Project: JBoss VFS
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.1.3.SP1
>            Reporter: Toshiya Kobayashi
>            Assignee: Ales Justin
>         Attachments: jboss-vfs.jar
>
>
> When resolving virtual files,
> 1. DefaultVFSRegistry checks expiration of root context by IterableTimedVFSCache.findContext() which is implemented based on TimedCachePolicy.getValidKeys()
> 2. If the context is expired, a new context is created and CachePolicyVFSCache.putContext() is called, but the method checks the existence of cache entry by TimedCachePolicy.peek() which doesn't care about its expiration. Then the new entry won't be inserted into the cache and the expiration time of the old entry won't be updated.
> So once cache entries are expired, caching won't work and contexts will be created again and again.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira