[MGNLCACHE-82] Runtime reconfiguration without killing the caches Created: 05/Feb/15  Updated: 18/Feb/15  Resolved: 18/Feb/15

Status: Closed
Project: Cache Modules
Component/s: configuration
Affects Version/s: 5.4
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Roman Kovařík Assignee: Roman Kovařík
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLCACHE-32 Upgrade Ehcache to the latest (2.10.0) Closed
supersession
is superseded by MGNLCACHE-75 Make it possible to share default con... Closed
Template:
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)

 Description   

Currently we call CacheManager.shutdown() which deregister it and the content of living caches is lost (probably because the persistence is not supported in non-re edition).

If we want to keep live caches:

  1. We can't call shutdown on restart.
  2. At least some of the properties should be configurable at runtime (see net.sf.ehcache.config.Configuration.DynamicProperty). The change of defaultCacheConfiguration is enough for us.
    Not sure how to change the configuration of an existing manager. We could test:

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