Use CFTRY/CFCATCH around your queries and do a little custom error handling. It goes a LONG way!
Dave ----- Original Message ----- From: "Carlisle, Eric" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Thursday, November 29, 2001 8:04 AM Subject: REPOST - cfquery timeout attribute We had an Oracle listener hang. This caused big problems in ColdFusion. The "timeout" attribute just didn't seem to work. I posted this here before and it was suggested that the timeout clock doesn't start until the SQL is sent. Since the listener was hung, I'm not sure how far CF went with the connection. In anycase, the unresponsive threads brought down a handful of servers just because one datasource was inoperable. Is there anyway to avoid this in the future? It seems like CFs error correction (timeout in the CF admin) flew out the window. Can I get more error correction by using ADO? Thanks :) EC . ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
