[MAGNOLIA-3447] Cache configuration contains reference to the commenting configuration Created: 04/Dec/10  Updated: 17/Jan/11  Resolved: 06/Dec/10

Status: Closed
Project: Magnolia
Component/s: cache
Affects Version/s: 4.4
Fix Version/s: 4.4.2

Type: Bug Priority: Critical
Reporter: Danilo Ghirardelli Assignee: Ondrej Chytil
Resolution: Fixed Votes: 0
Labels: FlushByComments, cache
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 7, java 1.6.0_22, in memory repository.


Attachments: Text File cache.patch     Text File stacktrace.txt    
Template:
Patch included:
Yes
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   

I'm upgrading from 4.3.8 to 4.4, and at the boot there is this below. The new dispatcher is added to the filter, and magnolia.update.auto is set to true. Even after cleaning the magnolia-data folder (is just an im-mem repo for local developing), the exception is still there. The searched class is not in the classpath (I'm not including the commenting module nor the PUR one).

4.12.2010 10:37:46 WARN info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toBean(Content2BeanProcessorImpl.java:81) | can't resolve class for node /modules/cache/config/configurations/default/flushPolicy/policies/FlushByComments
java.lang.ClassNotFoundException: info.magnolia.module.commenting.cache.ReferencedPageFlushPolicy



 Comments   
Comment by Danilo Ghirardelli [ 04/Dec/10 ]

You repo is offline at the moment so I can't check with version 4.4.1

Comment by Danilo Ghirardelli [ 04/Dec/10 ]

After the warning, the application is not working, giving a java.lang.AbstractMethodError to each request.

Comment by Jan Haderka [ 06/Dec/10 ]

This configuration is bootstrapped by the commenting module that also contains the said class. So to have this configuration, you must have originally installed the commenting module. Now since you removed the module, class can't be resolved and you need to also remove this configuration to get rid of the error.

Comment by Danilo Ghirardelli [ 06/Dec/10 ]

Absolutely no. I never used that module, and as I stated before, I'm doing a clean start with in-momery repository, so there should be no error unless I have that configuration within my xml files, and I already checked those.
I checked the files on the branch and here it is:

config.modules.cache.config.configurations.default.xml

contains the reference to the info.magnolia.module.commenting.cache.ReferencedPageFlushPolicy class at line 1614. I'm talking about your files deployed in the jars, not my configuration. Would you mind explaining why that reference is there even if the module is not a required dependency? Also I'd like to know how the 4.4 would start without the said module...

Comment by Danilo Ghirardelli [ 06/Dec/10 ]

Attached there is the patch to let the application start again, I suppose the removed lines should be moved to the appropriate bootstrap file of the commenting module.

Comment by Jan Haderka [ 06/Dec/10 ]

Darn, haven't seen that reference. This policy is installed by the commenting module, but when the complete cache configuration was exported it was indeed exported with the commenting setting in. Thanks & sorry about the misunderstanding.

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

increasing priority as it prevents CE installations from working properly

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