[MGNLCACHE-187] Uuid-key-mapping does not work since ehcache3 Created: 26/Oct/17  Updated: 14/Apr/20  Resolved: 08/Apr/20

Status: Closed
Project: Cache Modules
Component/s: ehcache3
Affects Version/s: 5.5.4
Fix Version/s: 5.6.4, 5.8.3, 5.9.1

Type: Bug Priority: Neutral
Reporter: Roman Kovařík Assignee: Federico Grilli
Resolution: Fixed Votes: 1
Labels: maintenance
Remaining Estimate: 1h
Time Spent: 17m
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLCACHE-173 New ehCache3 submodule Closed
relation
Template:
Patch included:
Yes
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Testcase included:
Yes
Date of First Response:
Epic Link: Support
Sprint: Maintenance 1, Maintenance 2
Story Points: 0

 Description   

Ehcache3 uses persistent disk store by default = copy on read (or write or both).
That means the mapping which we put into map retrieved by info.magnolia.module.cache.cachepolicy.Default#getUUIDKeySetFromCacheSafely
are not saved in the same object which is cached but into a copy.

The possible solution is to create a separate config for uuid-key-mapping without the disk store.

This used to work with

  • Ehcache2 since that one is not persistent by default
  • Ehcache15 even though was also persistent

Generated at Sun Feb 11 23:53:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.