If your CF server got stuck and that there doesn’t seem to be an option to find out what’s happening inside of the black box – there IS a real possibility in ColdFusion MX.
Regarding CFs Java foundation, there is a way to produce Java stack traces in CF. Macromedia provides a technote about how to do it, it’s not difficult, you just have to start your CF instance in a certain manner to be able to “let it crash with control”. Dumping each threads stack trace, you might be able to find the responsible template for your issues.
This procedure worked great for one of my customers, they were able to identify a long running CFHTTP call on one of the pages as a point of failure to stop their machine working correctly.
OK, this is an old post, but if anyone reads it and wants an easier way to get stack traces, I found a link to something called FusionReactor (fusion-reactor.com) which you can run for free and which does stack traces for you. It’s not been out for long but so far I really like it…
Comments on this entry are closed.