Sounds like a request timeout, not a query timeout.  If the request
times out, the request simply terminates with a non-graceful failure,
and no way to catch it.  If it were a query timeout, your
CFTRY..CFCATCH would catch it exactly as your expected.

You can use CFSETTING to increase the request timeout.  Don't make it
ridiculously long (to protect the server), but maybe start at two
minutes, and up it by another minute each time until you
get a successful run.  Just keep in mind that the tag takes a value
specified in seconds, not minutes.

cheers,
barneyb

On Thu, 13 Jan 2005 23:31:36 -0600, Nick Baker <[EMAIL PROTECTED]> wrote:
> Using a MX and MySQL on a shared server. I am running some updates in a
> scheduled event, i.e., no user there to reload the page.
> 
> I have an UPDATE CFQUERY in a loop, where it loops a variable number of
> times, up to about 75.
> The query times out somewhere in the 10 to 30th loop
> 
> Query "timeout" is set to 15000 milliseconds, but it always times out in
> the 5 second range.
> 
> I am using a CFTRY and CFCATCH which catches problems I can induce, e.g.,
> misspelled variable or DNS,  but it doesn't catch the timeout?
> 
> Question 1. Any ideas on how to beat the time out?
> 
> Question 2. Even if I can beat the timeout, I would like to trap all errors
> and log in an error log, and continue on completing the process. But, the
> durn thing is aborting with the timeout errors.
> 
> Any ideas, suggestions, etc?
> 
> Thanks,
> 
> Nick
> 
> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Discover CFTicket - The leading ColdFusion Help Desk and Trouble 
Ticket application

http://www.houseoffusion.com/banners/view.cfm?bannerid=48

Message: http://www.houseoffusion.com/lists.cfm/link=i:4:190390
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to