It sounds like getting a stack trace during execution might help you prove what the offending line of code is. I know I've sung this song a lot, but SeeFusion is an excellent resource for this and I love it.
www.seefusion.com ~Brad -----Original Message----- From: Dave Phillips [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 05, 2006 11:05 AM To: CF-Talk Subject: Re: Query of Query Timeout Here's another question. I added a <cfoutput>#getTickCount()#</cfoutput><br> line directly after my CFSEARCH tag (and before my QofQ) and now the timeout is happening on that CFOUTPUT tag. Taht seems very strange. It is almost as if the CFSEARCH tag is the one timing out, but CF is reporting it on the next available tag. Is it possible that if the CFSEARCH takes longer than the 60 second limit, that as soon as Verity has returned handling to CF, the request then terminates because it has exceeded the 60 seconds? If so, what accounts for the fact that some searches actually finish and report in the server log as taking longer than the 60 seconds? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:262931 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
