enhance memory service with ehcache to provide LRU management and tie in with other caching (eg hibernate)
GENERAL
TESTING
GENERAL
TESTING
Description
The current memory service works ok in a cluster, and provides a central point for management, but it is not as configurable as a mainstream caching provider and does not have many eviction strategies. If we used ehcache underneath the current memory service we would get this abilit along with a JMX interface that we could use with JMX based tools. This would remove the need to clear the cache, or to put time outs on the cached data. (where its backed by event invalidation).
2.5.0 QA has been completed. Unfortunately, there were not resources available to specifically test this issue. If you find this to still be a problem in the latest release (at this point 2.5.2), please reopen the JIRA and add the latest affects version.
Lance Speelmon September 10, 2007 at 11:36 AM
I went ahead and committed this code to trunk. If we find any major problems we can always back it out. Best, L
Ian Boston September 9, 2007 at 2:31 PM
Patch of changes to memory, event and authz to make them use a ehcache backend.
The current memory service works ok in a cluster, and provides a central point for management, but it is not as configurable as a mainstream caching provider and does not have many eviction strategies. If we used ehcache underneath the current memory service we would get this abilit along with a JMX interface that we could use with JMX based tools. This would remove the need to clear the cache, or to put time outs on the cached data. (where its backed by event invalidation).