Compile errors in 5.3.8.189

Description

Since upgrading one of our servers to 5.3.8.189, every day or two we see a surge of Compile errors in our Application log. The error messages come thick and fast for a few minutes and then taper off over an hour or two. Most recently we were using the 5.3.8.167 RC and didn’t see these errors.

The error messages are similar to:

Class [surfschool.admin.customer_cfm$cf$3cd] is invalid or doesn't exist;Class [surfschool.admin.customer_cfm$cf$3cd] is invalid or doesn't exist

The stack trace is similar to:

java.lang.ClassNotFoundException: Class [surfschool.admin.customer_cfm$cf$3cd] is invalid or doesn't exist
at lucee.commons.lang.PhysicalClassLoader.findClass(PhysicalClassLoader.java:161)
at lucee.commons.lang.PhysicalClassLoader.loadClass(PhysicalClassLoader.java:142)
at lucee.commons.lang.PhysicalClassLoader.loadClass(PhysicalClassLoader.java:125)
at lucee.commons.lang.PhysicalClassLoader.loadClass(PhysicalClassLoader.java:119)
at lucee.runtime.MappingImpl.getPhysicalClass(MappingImpl.java:259)
at lucee.runtime.PageSourceImpl.loadPhysical(PageSourceImpl.java:354)
at lucee.runtime.PageSourceImpl.loadPageThrowTemplateException(PageSourceImpl.java:237)
at lucee.runtime.PageSourceImpl.loadPage(PageSourceImpl.java:1014)
at lucee.runtime.PageContextImpl._doInclude(PageContextImpl.java:1026)
at lucee.runtime.PageContextImpl._doInclude(PageContextImpl.java:923)
at lucee.runtime.PageContextImpl.doInclude(PageContextImpl.java:904)
at surfschool.admin.application_cfc$cf$28i.udfCall(/surfschool/admin/Application.cfc:155)
at lucee.runtime.type.UDFImpl.implementation(UDFImpl.java:106)
at lucee.runtime.type.UDFImpl._call(UDFImpl.java:344)
at lucee.runtime.type.UDFImpl.call(UDFImpl.java:217)
at lucee.runtime.ComponentImpl._call(ComponentImpl.java:684)
at lucee.runtime.ComponentImpl._call(ComponentImpl.java:572)
at lucee.runtime.ComponentImpl.call(ComponentImpl.java:1911)
at lucee.runtime.listener.ModernAppListener.call(ModernAppListener.java:437)
at lucee.runtime.listener.ModernAppListener._onRequest(ModernAppListener.java:216)
at lucee.runtime.listener.MixedAppListener.onRequest(MixedAppListener.java:44)
at lucee.runtime.PageContextImpl.execute(PageContextImpl.java:2457)
at lucee.runtime.PageContextImpl._execute(PageContextImpl.java:2447)
at lucee.runtime.PageContextImpl.executeCFML(PageContextImpl.java:2418)
at lucee.runtime.engine.Request.exe(Request.java:44)
at lucee.runtime.engine.CFMLEngineImpl._service(CFMLEngineImpl.java:1179)
at lucee.runtime.engine.CFMLEngine...

 

Related forum topic

Environment

Windows Server 2019
OpenJDK 11.0.7
Tomcat 9.0.35

Attachments

1

is caused by

Activity

Robert Diamond 1 September 2021 at 18:38

Same thing (I think?) here… It does seem tied to memory usage going up (goes up more the more of these errors we see). On 5.3.8.201 here.

Simon Goldschmidt 12 August 2021 at 22:45
Edited

The line preceding the error reads:

The compiler seems to run into these error when it loads a class from “ClassLoader” rather than from “binary”.

Immediately below the error is the line:

So it looks like the page is subsequently compiled and run without impacting our application.

Simon Goldschmidt 12 August 2021 at 22:38

The restart fixed things for a few days, then we have seen the errors recur. Here is a sample of a more complete stack trace from a log file:

 

Michael Born @ Ortus 11 August 2021 at 15:11

If you’re not seeing any updated logging info, I think you need to enable DEBUG-level logging in the lucee web administrator for the application log. Micha added logging statements, but you need to configure the logs to show that info or log4j will suppress them.

Simon Goldschmidt 7 August 2021 at 00:47

The logs for 5.3.8.196 look the same as they were for 5.3.8.189. I have set up a server to try again. I noticed that we didn't restart the server after updating the version through the Lucee Administrator… perhaps a restart after updating will be different. I’ll report what we notice.

 

Fixed

Details

Assignee

Reporter

Priority

Labels

Fix versions

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Affects versions

Created 17 July 2021 at 00:46
Updated 29 August 2022 at 13:52
Resolved 29 August 2022 at 13:52