cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Freddy Exposito (JIRA)" <>
Subject [jira] [Commented] (CXF-5420) Issue with EhCacheTokenStore using default LRU.
Date Tue, 26 Nov 2013 15:16:36 GMT


Freddy Exposito commented on CXF-5420:


Calling 'updateUpdateStatistics' won't work because it's actually setting 'lastUpdateTime'
(not 'lastAccessTime'). What do you think about calling 'resetAccessStatistics' on the newly
created Element? I think that will do.


> Issue with EhCacheTokenStore using default LRU.
> -----------------------------------------------
>                 Key: CXF-5420
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.6.10, 2.7.7
>            Reporter: Freddy Exposito
>            Assignee: Colm O hEigeartaigh
>            Priority: Minor
> HI All,
> The Ehcache TokenStore implementation ( EHCacheTokenStore)
is evicting wrong elements from the token store. It’s happening very randomly in a heavy
multi-thread application but at some point is trying to get a DerivedKeyToken (added before
sending request to the server) that was evicted before the response was returned.
> I actually  see the issue in the Ehcache Element implementation (
because the constructor of class Element  that the CXF EHCacheTokenStore implementation is
using is not setting ‘lastAccessTime’ in the constructor. As lastAccessTime is being zero
by default, all the DerivedKeyToken elements in the token store have lastAccessTime=0 and
there is a possibility that a wrong element is evicted because the default ehcache LRU policy
uses the ‘lastAccessTime’ to perform eviction.
> I reported the issue to EHcache already although I haven’t received answer from them.
In the meantime, would you consider to update EHCacheTokenStore to use a more suitable Element
constructor that allows setting ‘lastAccessTime’ properly?
> Thanks,

This message was sent by Atlassian JIRA

View raw message