Magnolia 6.2.49 known issues
Cache misses when using ServeUntilRecachedCachePolicy
Since the introduction of the RerouteCacheEntry (MGNLCACHE-369), you may experience cache misses because the re-route cache entries aren’t dereferenced in the ServeUntilRecachedCachePolicy.
Instead, getLastModificationTime() is called on the RerouteCacheEntry, which leads to UnsupportedOperationException errors:
ERROR info.magnolia.module.cache.filter.CacheFilter 05.09.2024 03:51:12 -- A request started to cache but failed with an exception (UnsupportedOperationException: ). [url=https://demopublic.magnolia-cms.com/dam/jcr:58c420b6-fa30-4578-8af0-c062ba51e5fb/cultural.svg]
ERROR info.magnolia.module.cache.filter.CacheFilter 05.09.2024 03:51:14 -- A request started to cache but failed with an exception (UnsupportedOperationException: ). [url=https://demopublic.magnolia-cms.com/.resources/travel-demo-theme/img/logo-white.png]
ERROR info.magnolia.module.cache.filter.CacheFilter 05.09.2024 03:51:14 -- A request started to cache but failed with an exception (UnsupportedOperationException: ). [url=https://demopublic.magnolia-cms.com/.resources/travel-demo-theme/libs/lazysizes/lazysizes.min~2024-08-01-03-52-18-000~cache.js]In PaaS environments, rather than cache misses you may encounter 500 request errors for some requests, specifically those for the CSS and JS files, which will break the frontend and render your sites unusable.
| This issue is addressed in MGNLCACHE-383, with a fix coming with Magnolia 6.2.51. |
Workaround
Instead of the advanced caching strategies, switch to and use the default one.