[MAGNOLIA-4034] WARN java.lang.ClassNotFoundException: RenderableDefinitionModel$Factory on startup when migrating from 4.4.6 to 4.5 Created: 09/Mar/12  Updated: 09/Mar/12  Resolved: 09/Mar/12

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 4.5
Fix Version/s: 4.5.1

Type: Bug Priority: Minor
Reporter: Eric Hechinger Assignee: Eric Hechinger
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CE and EE


Issue Links:
Cloners
clones MAGNOLIA-4018 java.lang.ClassNotFoundException: Ren... Closed
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

 Description   

When migrating from 4.4.6 to 4.5, during the first start up of the server (before migration start), we have the following WARN.

2012-03-02 20:43:07,330 WARN gnolia.content2bean.impl.Content2BeanProcessorImpl: can't resolve class for node /server/rendering/freemarker/modelFactories/renderable
java.lang.ClassNotFoundException: info.magnolia.module.templating.freemarker.RenderableDefinitionModel$Factory
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1680)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1526)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at info.magnolia.objectfactory.DefaultClassFactory.forName(DefaultClassFactory.java:55)
at info.magnolia.content2bean.impl.Content2BeanTransformerImpl.resolveType(Content2BeanTransformerImpl.java:128)
at info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toBean(Content2BeanProcessorImpl.java:91)
at info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toMap(Content2BeanProcessorImpl.java:196)
at info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toBean(Content2BeanProcessorImpl.java:108)
at info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toMap(Content2BeanProcessorImpl.java:196)
at info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toBean(Content2BeanProcessorImpl.java:108)
at info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toBean(Content2BeanProcessorImpl.java:82)
at info.magnolia.content2bean.Content2BeanUtil.toBean(Content2BeanUtil.java:198)
at info.magnolia.objectfactory.ObservedComponentFactory.transformNode(ObservedComponentFactory.java:212)
at info.magnolia.objectfactory.ObservedComponentFactory.onRegister(ObservedComponentFactory.java:197)
at info.magnolia.objectfactory.ObservedComponentFactory$2.doExec(ObservedComponentFactory.java:155)
at info.magnolia.objectfactory.ObservedComponentFactory$2.doExec(ObservedComponentFactory.java:146)
at info.magnolia.cms.security.SilentSessionOp.exec(SilentSessionOp.java:71)
at info.magnolia.context.MgnlContext.doInSystemContext(MgnlContext.java:403)
at info.magnolia.context.MgnlContext.doInSystemContext(MgnlContext.java:376)
at info.magnolia.objectfactory.ObservedComponentFactory.load(ObservedComponentFactory.java:146)
at info.magnolia.objectfactory.ObservedComponentFactory.reload(ObservedComponentFactory.java:142)
at info.magnolia.objectfactory.ObservedComponentFactory.onEvent(ObservedComponentFactory.java:138)
at info.magnolia.cms.util.ObservationUtil$ObservationBasedDelayedExecutor$1.run(ObservationUtil.java:236)
at info.magnolia.cms.util.DelayedExecutor$RunnableWrapper.run(DelayedExecutor.java:105)
at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(Unknown Source)
at java.lang.Thread.run(Thread.java:680)



 Comments   
Comment by Eric Hechinger [ 09/Mar/12 ]

When migrating from 4.4.6 to 4.5, during the first start up of the server (before migration start), we have this warning log.
This is not an issue, just a WARN message without impact on the running application. This message disapear after the migration.

Reason of this message:
This Happens because we use freemarker in core before the version handlers are executed (in fact the module install UI that presents what the update will do uses freemarker).

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