Lucee/graph.cfm HttpServerError 500 /GlobalCFMLServlet

dev google-group-archive
1

Hi,
I get very often on Lucee 4.5.x an HttpServerError 500.
NeRelic says it’s in
lucee/graph.cfm HttpServerError 500 /GlobalCFMLServlet

in exception.log is this:

"
“ERROR”,“ajp-bio-8009-exec-9”,“08/30/2015”,“21:55:14”,“”,";file or
directory
D:/websites/mydomain.com/WEB-INF/railo/temp//graph/DB11EC56-87F5-4C56-A6DE59A9785226F7.png
not exist;file or directory
D:/websites/mydomain.com/WEB-INF/railo/temp//graph/DB11EC56-87F5-4C56-A6DE59A9785226F7.png
not exist
at
railo.commons.io.res.util.ResourceUtil.toResourceExisting(ResourceUtil.java:217):217
at
railo.commons.io.res.util.ResourceUtil.toResourceExisting(ResourceUtil.java:182):182
at railo.runtime.tag.Content._doStartTag(Content.java:157):157
at railo.runtime.tag.Content.doStartTag(Content.java:145):145
at
graph_cfm$cf.call(D:\websites\mydomain.com\WEB-INF\railo\context\graph.cfm:16):16
at railo.runtime.PageContextImpl.doInclude(PageContextImpl.java:925):925
at railo.runtime.PageContextImpl.doInclude(PageContextImpl.java:829):829
at
application_cfc$cf.udfCall(/railo-context-compiled/Application.cfc:58):58
at railo.runtime.type.UDFImpl.implementation(UDFImpl.java:109):109
at railo.runtime.type.UDFImpl._call(UDFImpl.java:326):326
at railo.runtime.type.UDFImpl.call(UDFImpl.java:227):227
at railo.runtime.ComponentImpl._call(ComponentImpl.java:639):639
at railo.runtime.ComponentImpl._call(ComponentImpl.java:522):522
at railo.runtime.ComponentImpl.call(ComponentImpl.java:1754):1754
at
railo.runtime.listener.ModernAppListener.call(ModernAppListener.java:404):404
at
railo.runtime.listener.ModernAppListener._onRequest(ModernAppListener.java:220):220
at
railo.runtime.listener.ModernAppListener.onRequest(ModernAppListener.java:100):100
at railo.runtime.PageContextImpl.execute(PageContextImpl.java:2228):2228
at railo.runtime.PageContextImpl.execute(PageContextImpl.java:2195):2195
at
railo.runtime.engine.CFMLEngineImpl.serviceCFML(CFMLEngineImpl.java:353):353
at railo.loader.servlet.CFMLServlet.service(CFMLServlet.java:29):29
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722):722
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304):304
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210):210
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224):224
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169):169
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472):472
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168):168
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100):100
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118):118
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:405):405
at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:200):200
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:515):515
at
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:302):302
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source):-1
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source):-1
at java.lang.Thread.run(Unknown Source):-1

Maybe it’s some code with a captcha creation?

How do I trace this error down? Where is the origin?

Regards
Thorsten

2

Thanks Tony, probably it’s the captcha. Is there a way to prevent raising this error, because it’s poluting the error logs.

3

That occurs with captchas that have been generated and discarded but are
trying to be accessed from a cache of some kind. See this discussion in the
Railo group - https://groups.google.com/d/msg/railo/k6LxC0L7Tg4/MNYyw6yza6sJ

4

I’m not certain it will help you in your situation, however…

My observations of this occurring in my logs in the past were tied to using
the default global error template (error.cfm) that was set in Railo. So
when a non-existent path, such as a captcha image, was requested, an
exception was thrown. Since the exception isn’t handled by any application
level catches, it’s logged by Railo/Lucee. Changing error.cfm to
error-public.cfm, in the admin, silences this exception as the only return
is a message stating something along the lines of “We’re sorry but an error
has occurred”. At that point I do not see those exceptions in my logs;
though that may not be ideal if there was some other hard exception that
you would want to know about (I’ve never seen anything else occur other
than that exception personally). That’s possibly where creating a custom
template file can be useful.

The exception itself is mostly harmless, I’d think. If anything, note what
the exact exception is and then make a custom template that tries to filter
that specific occurrence out so you can still catch others.

I wrote a short blog post a while back about changing the default error
template

Cheers.

5

I dev mode, I’ve found the Coldbox debugger had the same issue.On Monday, September 28, 2015 at 9:56:54 AM UTC-7, Tony Junkes wrote:

I’m not certain it will help you in your situation, however…

My observations of this occurring in my logs in the past were tied to
using the default global error template (error.cfm) that was set in Railo.
So when a non-existent path, such as a captcha image, was requested, an
exception was thrown. Since the exception isn’t handled by any application
level catches, it’s logged by Railo/Lucee. Changing error.cfm to
error-public.cfm, in the admin, silences this exception as the only return
is a message stating something along the lines of “We’re sorry but an error
has occurred”. At that point I do not see those exceptions in my logs;
though that may not be ideal if there was some other hard exception that
you would want to know about (I’ve never seen anything else occur other
than that exception personally). That’s possibly where creating a custom
template file can be useful.

The exception itself is mostly harmless, I’d think. If anything, note what
the exact exception is and then make a custom template that tries to filter
that specific occurrence out so you can still catch others.

I wrote a short blog post a while back about changing the default error
template -
If Your Error Template For Railo Is error.cfm In Production, Change It! - A Blog By Tony Junkes

Cheers.