Skip to main content
J
JorgeACT
Participant
April 4, 2025
Question

After updating Coldfusion 2021 to latest release 18 CFR reports stopped working

  • April 4, 2025
  • 1 reply
  • 443 views

Hi All, 

 

After updating my Coldufsion 2021 server to the latest release (18 went from 2021,0,0,323925 to 2021,0,18,330341) to mitigate vulnerabilities CFR reports stopped working and I'm getting the following errors:

 

coldfusion.runtime.report.Report$ReportCompilationException: Report compilation error.
at coldfusion.runtime.report.Report.compileXml(Report.java:840)
at coldfusion.runtime.report.Report._compileReport(Report.java:281)
at coldfusion.runtime.report.Report.compileReport(Report.java:176)
at coldfusion.runtime.report.Report.runReport(Report.java:425)
at coldfusion.tagext.report.ReportTag.doEndTag(ReportTag.java:626)
at cfrpt_insumos_pdf2ecfm955247095.runPage(/app/residente/rpt_insumos_pdf.cfm:14)
at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:257)
at coldfusion.tagext.lang.IncludeTag.handlePageInvoke(IncludeTag.java:749)
at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:578)
at coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:65)
at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:613)
at coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:43)
at coldfusion.filter.MonitoringFilter.invoke(MonitoringFilter.java:40)
at coldfusion.filter.PathFilter.invoke(PathFilter.java:162)
at coldfusion.filter.IpFilter.invoke(IpFilter.java:45)
at coldfusion.filter.LicenseFilter.invoke(LicenseFilter.java:30)
at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:97)
at coldfusion.filter.BrowserDebugFilter.invoke(BrowserDebugFilter.java:81)
at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:28)
at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38)
at coldfusion.filter.NoCacheFilter.invoke(NoCacheFilter.java:60)
at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38)
at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22)
at coldfusion.filter.CachingFilter.invoke(CachingFilter.java:62)
at coldfusion.CfmServlet.service(CfmServlet.java:231)
at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:311)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:199)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144)
at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:46)
at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:47)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:168)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144)
at coldfusion.inspect.weinre.MobileDeviceDomInspectionFilter.doFilter(MobileDeviceDomInspectionFilter.java:57)
at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:47)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:168)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:168)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:482)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:357)
at org.apache.coyote.ajp.AjpProcessor.service(AjpProcessor.java:448)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:936)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1791)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1190)
at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63)
at java.base/java.lang.Thread.run(Thread.java:834)

 

 

Report compilation error.Error at line 4 char 202: net.sf.jasperreports.engine.xml.JasperDesignFactory The specific sequence of files included or processed is: /app/residente/rpt_insumos_pdf.cfm, line: 14

 

1 reply

Charlie Arehart
Community Expert
Charlie ArehartCommunity Expert
Community Expert
April 5, 2025

Jorge, I have "good news" in that this is a known issue: not with update 18 but 17. And there IS a solution (which should be simple), and it's discussed in the technote for that update 17.

 

Before I elaborate, this is a good chance to point out that while cf updates are indeed cumulative (you can skip previous ones), it's still incumbent upon folks to read the technotes for each update you're skipping. I know it's like being told to floss. 🙂 But to be clear the admonition IS indeed indicated at the top of each update technote.

 

As for solving the problem, it should be simple. In fact the update 17 technote specifically mentions your error (that you'd offered at the bottom of your note) saying that if "the following error message appears: Error at line 4... net.sf.jasperreports.engine.xml.JasperDesignFactory", you should "Clear the Felix cache and restart ColdFusion."

 

Later in the technote it points more specifically (rated to other errors) that the Felix cache is found at <cf_home>/cfusion/bin/felix-cache. I appreciate it's not all as clear as it could be", and it's understandable that one could miss it. 😞

 

Again what you'd want to do is stop cf, delete that folder, then start cf.

 

Then test your app and let us know how it goes.

 

Finally, folks should probably just get in the habit of doing this step after each cf update. It forces cf to rebuild its libraries related to packages. And any one update (or multiple ones you skip) may entail such changes, where this step can do some "spring cleaning" to your benefit. There's no reason NOT to. In fact I'm hoping Adobe will find a way to automate it, or at least more clearly recommend it as a post-update step--and not just for updates that DO entail package updates, because again people may skip some.

 

Hope that helps. 

/Charlie (troubleshooter, carehart. org)
J
JorgeACTAuthor
Participant
April 13, 2025

Thank you for your response Charlie, actually we removed the "presentations" package and that seemed to solve the issue. I'm a bit embarrassed that the answer was there all along, I have to update to version 19, what do you think I'm doing first?

 

Regards!

Charlie Arehart
Community Expert
Charlie ArehartCommunity Expert
Community Expert
April 13, 2025

Glad you got things going. While the removal of the presentations package may have "helped", it's not really the right solution in that doing the clear of the felix-cache folder is specifically indicated by Adobe for the error you got. 🙂 It's also beneficial to help other problems you may hit. Finally, you may eventually have someone want to use something in the presentation package, though perhaps not. 

 

And yes, it (the felix-cache clear) is something to do after update 19 as well. 🙂 

/Charlie (troubleshooter, carehart. org)
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices