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:

• The name of the property that holds the name of the default content caching configuration
• The name of the default content caching configuration

It probably shouldn't be used for at least one of those two. The existence of AbstractCacheModule.DEFAULT_CACHE_CONFIG suggests that the value of CacheFilter.DEFAULT_CONTENT_CACHING_CONFIGURATION should actually be "defaultContentCachingConfigurationName" instead of "defaultPageCache".