I'm see that CF 2021 SQL exception dumps have a bunch of stack frames inside the underlying base classes, before they get to the actual cf code that made the call. Ones like these: • macromedia.jdbc.sqlserver.base.BaseExceptions.b • macromedia.jdbc.sqlserver.base.BaseExceptions.a • macromedia.jdbc.sqlserver.tds.s.rZ • macromedia.jdbc.sqlserver.tds.s.a • macromedia.jdbc.sqlserver.SQLServerImplStatement.ch • etc Screen shot below, and it goes on, first cf call is at frame 14. I don't remember this from prior CF versions, is it new? More to the point, can I suppress all that?

It's done this for as long as I can remember. Stack traces can be very useful for debugging so I've never even thought of suppressing the tag context part.

I'm not sure I recall it spewing all the internals stuff out in the context section of the exception before though? In the full stack trace, sure. ? I only have CF2021 and 2023 here to monkey with (and TBH can't be arsed spinning up the containers and querying a DB badly and checking what gets spat out.

Tag context I want of course, what I have no use for are the stack frames inside macromedia.jdbc.sqlserver and the like. Not actionable, clutter, to me. I don't remember that happening in the past.

I've been noticing the SQL Server sections too; I don't recall previously having to scroll past all of those to get to the actual code error line

Right well I'd raise a ticket with Adobe then, and perhaps rattle @Mark Takata (Adobe)'s cage. He loves the attention. Just don't feed him. Especially after midnight.

From my understanding, it is the result of fixing a ticket where someone didn't like that we were suppressing part of the return of an object's meta data, or some such thing. I don't remember the ticket (I can check and see if I remember who it was) but at the time everyone seemed very onboard with the change (because I don't think we realized the downstream effects, i.e. that it would expose information on ALL dumps, including ones that had a ton of meta data we didn't actually care about.

Mmm. Beware the unintended consequences! It'd be cool to get rid of that stuff, but I'll live.

I'll need to hit up an engineer to confirm, but yeah. Mildly annoying, but occasionally extremely useful.