[
https://issues.apache.org/jira/browse/FC-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18007383#comment-18007383
]
Ben Manes commented on FC-327:
------------------------------
javax.cache was abandoned (rejected by jakarta). It has the option
{{storeByValue}} to serialize or not, which the standard requires to be
defaulted to on, so you might have needed to set that. Its api is not very good
but its usable for simple cases where you want end users to plug in their own,
e.g. hibernate's cache.
Last I looked, Hazelcast used an unbounded cache and a scheduled task to
periodically shrink it below a high watermark. That meant it was fast as a
ConcurrentHashMap but a bit unsafe.
Ehcache v2 is end of life. Version 3 has [performance
problems|https://gist.github.com/ben-manes/6312727adfa2235cb7c5e25cae523ad0]
and is not well maintained.
fwiw Infinispan, Coherence, and Redisson use Caffeine as their local cache.
> Upgrade from ehcache v2
> -----------------------
>
> Key: FC-327
> URL: https://issues.apache.org/jira/browse/FC-327
> Project: FORTRESS
> Issue Type: Improvement
> Affects Versions: 3.0.0
> Reporter: Shawn McKinney
> Priority: Major
> Fix For: 4.0.0
>
>
> Fortress core uses ehcache v2. It is getting long in tooth, has a number of
> CVE's, and needs to be replaced. Here we'll look at alternatives.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
