[jira] [Assigned] (CAMEL-6189) Camel cache: CamelCacheCheck and expiry on cached elements

["Claus Ibsen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen reassigned CAMEL-6189:
----------------------------------

    Assignee: Claus Ibsen
    
> Camel cache: CamelCacheCheck and expiry on cached elements
> ----------------------------------------------------------
>
>                 Key: CAMEL-6189
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6189
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-cache
>    Affects Versions: 2.10.0, 2.11.0
>         Environment: Windows
>            Reporter: Henrik Filtenborg Sørensen
>            Assignee: Claus Ibsen
>              Labels: cache
>             Fix For: 2.11.0
>
>         Attachments: cacheCheckHonorsExpiry.patch
>
>
> The operation CamelCacheCheck does not check to see if the cache element is expired before setting the header CamelCacheElementWasFound. This is due to the way isKeyInCache() from EHCache works. 
> I believe the bug/quirk has existed since the very beginning of the camel-cache component. The patch is made against 2.11.0-SNAPSHOT.
> The patch uses getQuiet() instead of isKeyInCache(). getQuiet() checks for element expiry before returning the element from the cache. getQuiet does not alter the cache element in any way (usage statistics etc) but removes the element from the cache if it is expired.
> See the thread on Camel User Forum: http://camel.465427.n5.nabble.com/Camel-cache-CamelCacheCheck-and-expiry-on-cached-elements-td5729404.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira