[MGNLADVCACHE-46] Advanced flush policies trigger Advanced cache module restart Created: 20/Feb/15  Updated: 19/Jun/15  Resolved: 01/Jun/15

Status: Closed
Project: Advanced Cache
Component/s: None
Affects Version/s: None
Fix Version/s: 1.7

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

Issue Links:
causality
caused by MGNLADVCACHE-43 Use site configuration instead of con... Closed
supersession
is superseded by MGNLADVCACHE-50 Advaced flush policies should not wri... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

Policies write into JCR and consequently trigger restart of Advanced Cache Module too often.
This is causes by implementation of module lifecycle by MGNLADVCACHE-43
The easiest solution is to rename the config node to prevent restarting of whole module.



 Comments   
Comment by Roman Kovařík [ 23/Feb/15 ]

For review: https://git.magnolia-cms.com/gitweb/?p=enterprise/advanced-cache.git;a=shortlog;h=refs/heads/MGNLADVCACHE-46

Comment by Roman Kovařík [ 01/Jun/15 ]

Reopened:
Policies can't write into config workspace since config is registered to flush cache since 5.4.
Closed:
To be done in separate ticket: MGNLADVCACHE-50.

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