[MGNLCACHE-119] "The defaultPageCache property is not set for the cache CacheFilter, falling back to defaultPageCache." Created: 20/Jul/15 Updated: 31/Jul/15 Resolved: 29/Jul/15 |
|
| Status: | Closed |
| Project: | Cache Modules |
| Component/s: | None |
| Affects Version/s: | 5.4 |
| Fix Version/s: | 5.4.1 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Nils Breunese | Assignee: | Evzen Fochr |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 2.75h | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| 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: | |||||||||
| Sprint: | Sprint 3 (Kromeriz) | ||||||||
| Description |
|
On a Magnolia 5.4 installation with a cleanly bootstrapped cache module, we get the following log message on startup:
WARN info.magnolia.module.cache.filter.CacheFilter 20.07.2015 14:32:42 -- The defaultPageCache property is not set for the cache CacheFilter, falling back to defaultPageCache.
This message seems to be logged by CacheFilter:119. The code in oCacheModuleStart() checks if defaultContentCachingConfigurationName is null, and apparently it is, but it seems the way to set this variable is to make sure setDefaultContentCachingConfigurationName() gets called. The obvious way to make sure that happens is via Node2Bean, which would mean having a property called defaultContentCachingConfigurationName. This property indeed doesn't exist, but the log message suggests that it's a property called defaultPageCache that's missing, which is actually not missing. My theory is that CacheFilter.DEFAULT_CONTENT_CACHING_CONFIGURATION_NAME is used for two different things:
It probably shouldn't be used for at least one of those two. |
| Comments |
| Comment by Roman Kovařík [ 28/Jul/15 ] |
| Comment by Roman Kovařík [ 28/Jul/15 ] |
|
Reopened:
|