CF911: Easier thread dumps and stack traces in CF: how and why
Note: This blog post is from 2009. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.You may have heard the value of taking thread dumps or stack traces when trying to understand and resolve problems with CF. They can be valuable to see what's really running on your server at the time it may seem hung or slow to respond. The problem is that they can be challenging to obtain, so here's how to get them even more easily.
(If you're not familiar with the value of thread dumps or stack traces, read on. The resources I point to get help you to appreciate their usefulness.)
The link to the SeeStack is not valid. Can you please update that? And I’m sure it will be really helpful.
Another way to take thread dumps on CF6/7, which I've been doing for years, is to use a utility called SendSignal (http://www.latenight...). It requires console access - remote desktop in Window Server 2003 with the "Connect to Console" option enabled works also.
SendSignal <pid-of-jrun.exe> will write the thread dump out to the <servername>-out.log file in the runtime\logs directory.
I'm facing one problem with my CF10 server shutdown in every 1-2 . After looking into log it seems the problem might be due to IIS Connector tuning problem and I have already made that changes mentioned here( http://blogs.coldfus... ). I'm just curious to know how can I enable thread dump if any error occurred and my server went down.
NOTE: There is chances that the request might be generated from CF scheduled tasks.