This content has been marked as final. Show 6 replies
You could always do a cftry, and when it fails, dump the cfcatch structure into an email and send it to yourself. If nothing else, it might give you some more information.
Good Idea. I'll give it a (cf)try.
I catpured an error at 10:30 last night. The "type" is java.util.EmptyStackException.
Although the on-screen errormsg showed one error at line 87, the cfcatch dump shows TWO elements under TagContext. Both are CFINCLUDES, as shown below.
Is this meaningful to you?
RAW_TRACE at cfindex2ecfm2088046539.runPage(D:\Inetpub\tas\index.cfm:87)
RAW_TRACE at cfApplication2ecfc1561683104$funcONREQUEST.runFunction(D:\Inetpub\tas\Application.cfc:177 )
Thanks for your interest, Azadi.
The code on line 87 of index.cfm is as stated above:
The code in application.cfc line 177 is in the OnRequest function and states:
Again, I assure you that the template name variable referenced on line 87 is absolutely valid. I also presume that the Arguments.TargetPage template is valid as part of the CF framework structure.
I am stumped!
In index.cfm, add cfdump pageinfo to the mail you send yourself. In application.cfc, cfdump the arguments.