anithav86922272, I don't know that we can make much from that stack trace alone. It's a point in time representation of what was going on at the time the request was terminated by the Server Monitor (and someone setting it up to do that, as an option).
As for finding why it had taken so long PRIOR to that point (which could be as much the problem as what was going on AT that point), I'm afraid the server monitor alert email you got doesn't help with that.
Have you not had the problem again since? Or if so, did it start happening in relation to any change? There's always an explanation, and there are ways to use monitoring tools to understand where and how requests are "taking too long".
But that old Server Monitor didn't help with that very well--and it was removed in CF2018, replaced by a new better monitor. I realize you won't be interested in that, being on CF9.
Instead, there is a tool which IS both more modern and capablel and CAN be used with CF9, called FusionReactor. And it offers a nice low-impact profiling feature that would identify exactly what and where within that request it was doing whatever made it run long. There's even a 14-day free trial of it, at fusion-reactor.com. There are still other tools, which instead profile the entire CF engine rather than on a per-request basis, which isn't as helpful.
Hope that helps you now or in the future. And FWIW, there are consultants (like myself) who can help you in solving such problems via direct, remote consulting. If interested, I list such people or companies at cf411.com/cftrouble. But you can ask follow-up questions here, of course, and I or others may chime in with more for you to consider.
/Charlie (troubleshooter, carehart.org)
6
Replies
AdChoices