I'm seeing an issue with exception stack traces on...
# adobeb
bockensm
01/12/2024, 5:40 PMI'm seeing an issue with exception stack traces on CF2023 U6 in a shared hosting environment. When I catch an exception for site1 and dump it, the stack trace lists tagContext entries where templates point to site2 instead. Has anyone encountered anything like this? I can reliably replicate it in my environment when doing a cfhttp call with
throwonerror=truebockensm
01/12/2024, 5:42 PMIt almost feels like the stack trace is cached. The file that contains the caught exception isn't even listed in the stack trace.
j
James Harris
01/12/2024, 5:45 PMAssuming both of the sites are on the same server, running under the same CF 2023 instance, the two different sites could be using the same application name.
If that's not the case, check the Component cache and Cache web server paths settings in the caching tab of the admin.
b
bockensm
01/12/2024, 5:46 PMSame server, same instance, different application names
bockensm
01/12/2024, 5:54 PM"Component cache" is checked, "Cache web server paths" is not checked
j
James Harris
01/12/2024, 5:58 PMDoes turning that off resolve the issue?
b
bockensm
01/12/2024, 5:59 PMNope
bockensm
01/12/2024, 5:59 PMassuming you meant for me to uncheck "Component cache"
j
James Harris
01/12/2024, 6:01 PMYeah - that's what I meant. And dang.
j
jclausen
03/01/2024, 11:29 PMWhat is your “Inspect Templates” setting?
b
bockensm
03/04/2024, 1:48 PM@jclausen I'm not sure which setting you're referring to.
j
jclausen
03/05/2024, 10:47 PMSorry. I’ve been travelling this week. If you go in to the CF Admin, you will see a setting in the cache section for “Trusted Cache” - it allows you the option to select “Always”, “Once” or “Never”. Either way, this sounds like something you might want to report to Adobe.
b
bockensm
03/05/2024, 11:41 PMI would like to report this to Adobe, but I need a solid repro case before I have any faith they'll look into it and have a shot at helping me. I don't have any specific conditions that lead me to reliably reproducing this issue.
bockensm
03/05/2024, 11:45 PMThe "Trusted Cache" setting looks like a simple checkbox, not somewhere I can select an option. In any case, since it might be relevant, I'm asking our systems team to report the status of that checkbox to me.
j
jclausen
03/06/2024, 12:22 AMIf “Trusted Cache” is checked, then that means the template, once compiled will never be re-compiled ( `“inspectTemplates”:“never” in CFConfig ). If Adobe is using some sort of hash of the file contents to determine if the file is in the cache, then it’s possible that, if the two files are identical in contents, whichever one gets compiled first is the one that they are referencing for the location and line numbers.
b
bockensm
03/06/2024, 3:38 PMTrusted Cache is not enabled on the production server. I'm going to try to formal Adobe support route and see what that will yield.
2 Views