[MAGNOLIA-3432] cache: fails if the modification date is set multiple times Created: 02/Dec/10  Updated: 20/Feb/15  Resolved: 02/Dec/10

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 4.4
Fix Version/s: 4.4.1

Type: Bug Priority: Major
Reporter: Rakesh Vidyadharan Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File featuredBooks.ftl    
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
Date of First Response:

 Description   

It seems that the cache has issues
From the user list:


I just finished updating (a brand new install with all our content actually) to 4.4, and noticed that quite a few of our data modules (templates that return XML or HTML snippets) stopped functioning on the public instance. There are no issues on 4.3.8 with the template code, so I am not sure what exactly we need to do (other than disabling the cache for these templates). Any reason why the behavior has changed in 4.4?

java.lang.IllegalStateException: Can't get Last-Modified header : no or multiple values : [1291223564589, Wed, 01 Dec 2010 16:36:09 GMT]
                at info.magnolia.module.cache.filter.CacheResponseWrapper.getLastModified(CacheResponseWrapper.java:184)
                at info.magnolia.module.cache.executor.Store.makeCachedEntry(Store.java:119)
                at info.magnolia.module.cache.executor.Store.processCacheRequest(Store.java:85)
                at info.magnolia.module.cache.executor.CompositeExecutor.processCacheRequest(CompositeExecutor.java:65)
                at info.magnolia.module.cache.filter.CacheFilter.doFilter(CacheFilter.java:122)
                at 


 Comments   
Comment by Rakesh Vidyadharan [ 02/Dec/10 ]

We are not specifying any modification time in the template. I am attaching one of the templates that fail on the public instance.

Comment by Rakesh Vidyadharan [ 02/Dec/10 ]

A template that generates XML to drive a section of the main page.

Comment by Philipp Bärfuss [ 02/Dec/10 ]

I think it has nothing to do with the template but perhaps your renderer/model/servlet sets the modification date. Can you try if the 4.4.1-SNAPSHOT cache jar fixes the issue?

Thanks!

Comment by Magnolia International [ 02/Dec/10 ]

For the record, what happened is while fixing MAGNOLIA-3402, we accidentally removed the removeHeader() call in CacheResponseWrapper.replaceHeader() (in r39745).

Rakesh, do not hesitate to re-open the issue if the 4.1.1 snapshot Philipp linked to does not resolve your problem of course !

Comment by Philipp Bärfuss [ 03/Dec/10 ]

I linked to the core jar but should obviously be the cache jar.

Generated at Mon Feb 12 03:46:25 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.