I’m in the process of migrating an application to Lucee and one of the
things that I have throughout my code is cftry cfcatch blocks like this.
select *
from table
where (a = 1)
Everything is all caught properly so that the pages run, regardless of any
errors, and unless I explicitly trap the error to look at later I don’t
care why it hit the cftry block.
But in Lucee, everytime it hits one of these, It fires the ERROR part of
the logging and it’s filling up the application.log, datasource.log and
exception.log.
Is there any way to turn that off and prevent cftry catches from going into
those log files?
I just tried this with Lucee 5.1.1.65, only the datasource log got an
entry, which is expected
btw those datasource.log stacktraces are crazy verbose, looking at mine,
the error message was 4,
the previous from a more complex query was 10k
all the lucee.runtime.* and org.apache.* traces seem redundant, as web
developers we only really need to
see the CFML trace detailsOn Saturday, 4 February 2017 00:36:13 UTC+1, Sean Sidelko wrote:
I’m in the process of migrating an application to Lucee and one of the
things that I have throughout my code is cftry cfcatch blocks like this.
select *
from table
where (a = 1)
Everything is all caught properly so that the pages run, regardless of any
errors, and unless I explicitly trap the error to look at later I don’t
care why it hit the cftry block.
But in Lucee, everytime it hits one of these, It fires the ERROR part of
the logging and it’s filling up the application.log, datasource.log and
exception.log.
Is there any way to turn that off and prevent cftry catches from going
into those log files?