[
https://issues.apache.org/jira/browse/FC-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18001350#comment-18001350
]
Shawn McKinney commented on FC-327:
-----------------------------------
Have done a quick stab with Hazelcache. The migration isn't horrible but
running the tests, there's a noticeable degradation in performance. That's
because it requires serialization of objects stored in cache due to its
distributable characteristics. This is a step in the wrong direction and there
is no valid reason that I can think of that the cache would need to be
distributed. Yes, this means the cache entries will go stale. But, we're not
talking about often changed objects. We're caching stuff like roles,
constraints, policies. i.e. things that don't change all that often. A
reasonable cache timeout, say 10 or even 30 minutes should be fine.
> 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: [email protected]
For additional commands, e-mail: [email protected]
