There's a setting on the scheduled task page to set a timeout for that task
alone. You can set it there for 75 (I've got one running at 300). You can
also set the url to have a requesttimeout=75 on it as a variable which will
over-ride the default
http://127.0.0.1/index.cfm?requesttimeout=75
The
Scheduling in the betas was buggy too. Hope the production release didn't
carry those over.
-Original Message-
From: Michael Dinowitz [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 18, 2001 5:31 AM
To: CF-Talk
Subject: CF 5 scheduling
Has anyone had any problems with the scheduling in
At 08:31 AM 06/18/2001 -0400, you wrote:
Has anyone had any problems with the scheduling in CF 5? I've had CF 4.5.2
and earlier scheduled events running like a champ but 5 doesn't seem to want
to budge. Anyone else with this experience?
I've had bad luck with 4.5.2. But never used scheduling
I've had trouble with 5 and schedule routines too. I can run 'em fine
manually, but when the time comes for the server to run 'em, the
time just comes ... and goes. Nothing.
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe:
Did you import the old keys from the registry? You may have over-written the
HKEY_LOCAL_MACHINE\SOFTWARE\Allaire\ColdFusion\CurrentVersion\Schedule\Scrip
t key. This is the script to be run for a scheduled event.
I've had trouble with 5 and schedule routines too. I can run 'em fine
manually,
-Original Message-
From: Philip Brashear [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 19, 2001 1:51 PM
To: CF-Talk
Subject: Re: CF 5 scheduling
I've had trouble with 5 and schedule routines too. I can run 'em fine
manually, but when the time comes for the server to run 'em, the
time just
No problem here with scheduling after installing CF 5 pro subscription
upgrade.
- Original Message -
From: Michael Dinowitz [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Monday, June 18, 2001 8:31 AM
Subject: CF 5 scheduling
Has anyone had any problems with the scheduling in
What type of problems are you having? I had a scheduled verity update
template that ran fine until I upgraded. After the upgrade, the template was
crashing. After investigation, I found that the template took about 45-60
seconds to update (it is a large collection), and the default timeout was
I found the problem. There's a registry setting to specify the template that
a scheduled task has to use. When I built the new machine, this setting was
set right. When I moved the scheduler settings from the old machine to the
new one, it got overwritten. I'm writing this up as a paper for next
9 matches
Mail list logo
