This has been a common topic over the years. Per the general CFAdmin timeout setting, ColdFusion will not timeout a request while the request is waiting to receive all the data. The general ColdFusion timeout governs most everything else. However, SQL Server and Oracle drivers should support a database timeout, so the CFQUERY timeout attribute should work for those dbs.
The "Restart After X Unresponsive Requests" setting was implemented as a (ugly) workaround for accumulating database requests that have run long and initiated a bottleneck and queuing. The setting assumes that if you have X number of requests all waiting for long database requests (or other long events), that the database might be down. On the assumption that the application may continue to be otherwise usuable, the setting will cause ColdFusion to restart, killing all the hung requests (and any queued requests too), and perhaps when ColdFusion comes back up the database problem may have been resolved and the queuing (may or) may not occur again. -Steven Erat > -----Original Message----- > From: Earl, George [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 19, 2006 10:26 AM > To: CF-Talk > Subject: Timeout requests after XX seconds . . . > > I'm confused. > > If the 'Timeout requests after XX seconds' setting in CFAdmin > is set to > 60 seconds and a request (for us almost always a database > request) takes > longer than 60 seconds I get a message in the CF logs that 'The > unresponsive thread count is up to X.' When the request > completes I get > a message that 'The unresponsive thread count is down to X.' > and another > message that the offending template ran x seconds. > > I thought the purpose of the time out setting in CFAdmin was > to free up > the offending thread once the time out limit had been reached. But the > log file message implies that the thread is kept open until > the request > returns from the database at which time it is then terminated > and freed > up. > > Is this maybe two types of time outs - CF processing time outs vs. > database request time outs? And what I describe above is CF practicing > good database request housekeeping? > > Does it make sense that 1) if a thread is kept open until the request > returns from the database, even if that request goes beyond > the time out > setting in CFAdmin, and 2) if the CF processing on the returned answer > set is at most a couple of seconds, it would make sense to > not time out > these database requests? > > Running CF5 . . . :( > > Thanks! > > George ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:253518 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
