[MAGNOLIA-5676] uuid-cache key mapping is not updated Created: 13/Feb/14  Updated: 27/Feb/14  Resolved: 25/Feb/14

Status: Closed
Project: Magnolia
Component/s: cache
Affects Version/s: 4.5.9
Fix Version/s: 4.5.17

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

Issue Links:
Cloners
is cloned by MGNLCACHE-54 CLONE - uuid-cache key mapping is not... 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   

Cache key - uuid mapping is not kept in sync anymore. Actually it's not created at all. The UUID-cache-key cache is always empty. Due to this problem it's not possible to flush pages w/ comments from the cache in timely manner.

The issue is caused by call to MgnlContext.getAggregationState().getCurrentContent() in {{ info.magnolia.module.cache.executor.Store.processCacheRequest(HttpServletRequest, HttpServletResponse, FilterChain, Cache, CachePolicyResult)}} which seems to always return null now, while previously it returned the page content.

Quick solution is to change this call to invoke getMainContent() instead, the ultimate fix for the problem is to remove usage of deprecated API all together.


Generated at Mon Feb 12 04:07:21 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.