Every now and then we encounter error reports from our users about some page throwing a 503 error. In this particular case, today, we know exactly what page is throwing the 503 error and we’re investigating the issue.
But what bugs me is that in such cases the user gets 503 error, not Lucee error template - and nothing gets tracked into the Lucee error logs.
So, as you might understand, debugging such problems is bit of a pain. Any ideas on what typically causes this behavior (503, no error log)?
We’re using slightly older Lucee as of now:: Lucee 5.3.2.77 running on CentOS.
Typically, yes, something, that gets us going. In this particular case it was a non-declared cookie that template tried to set.
But that is not really the case, as our developers get access to Lucee logs to check for bugs in code, but they don’t have easy access to Tomcat / Apache logs.
My point being: IMHO, all errors oughta be logged on Lucee level
Bit late here, but for future reference: my Apache server throws 503’s:
ErrorDocument 503 /TomcatDown.html
So this request never gets to Tomcat, nor Lucee. Apache is the HTTP gateway. So Lucee will never have a change to log this request, as the request never got here.
