Barney has a good point that Eclipse's debugger can be used to inspect your server's threads even if CF isn't responding.
Here are some basic steps to connect Eclipse debugger to CF that I wrote up for a blog post once: "I added the following lines to my JVM startup args: -Xdebug -Xrunjdwp:transport=dt_socket,address=28000, server=y, suspend=n This tells the JVM to start in debug mode and listen on port 28000 for a debugger to connect. suspend=n tells the JVM NOT to suspend until the debugger connects. The port number is arbitrary, just make sure it's not already in use by something. Then I placed Eclipse in the Debug perspective, and chose Run > Debug... > Remote Java Application. I entered the address of my server for host and 28000 for the port number and then clicked Debug. This connected to my ColdFusion server's JVM and brought up all the threads in its existance." ~Brad ----- Original Message ----- From: "Barney Boisvert" <[EMAIL PROTECTED]> To: "cf-talk" <[email protected]> Sent: Wednesday, December 03, 2008 1:50 AM Subject: Re: I do not understand SeeStack at all > You running the standalone version of CF, or are you in JEE mode? If > the latter, launch the container in debug mode from Eclipse. Or if > that's not possible, set up the java debugging port on the JVM, launch > it normally, and connect to it with Eclipse. You can easily browse > through all the threads stacks, as well as easily identify hung > threads (and what they got hung on). > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:316171 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
