I have just done a clean install of CF8 on a Windows 2000 machine. I have a scheduled task I need to run every 15 minutes on this machine, and the machine does little else.
我刚刚在Windows 2000机器上完成了CF8的干净安装。我有一个计划的任务,我需要在这台机器上每15分钟运行一次,机器几乎没有其他功能。
The task is set up as normal through CF admin, but for some reason, when the task takes about 5 minutes to run it will complete fine (I can see this from debug output and from cfstat) but the scheduler will not reschedule the task.
任务通过CF管理员正常设置,但由于某种原因,当任务运行大约需要5分钟时,它将完成正常(我可以从调试输出和cfstat看到这一点),但调度程序不会重新安排任务。
The scheduling log shows that the task started to execute, but not entry that it was rescheduled. Eg:
调度日志显示任务开始执行,但不是重新安排的条目。例如:
[ProcessRecords] Executing at Wed May 20 10:30:00 BST 2009
I have been over my server timeouts. I have NO timeout in CF admin and this particular script has a <cfsetting requesttimeout="43200" /> tag set. There are no exceptions in the console logging. The last bit of console logging is the very last debug statement in my .cfm template.
我已经超过了我的服务器超时。我在CF admin中没有超时,这个特定的脚本有一个
I do notice that task that run in a shorter time, say for example under a minute, will reschedule as normal.
我注意到在较短时间内运行的任务,例如在一分钟之内,将正常重新安排。
Has anyone come across a problem like this before?
以前有人遇到过这样的问题吗?
I'm baffled. Any and all replies are appreciated!
我很困惑。任何和所有的回复表示赞赏!
Cheers, Ciaran
1 个解决方案
#1
not for nothing, but i've never seen anything like this with cf8. are you sure that you have the latest hotfix and jvm installed? this might have been something in cf8 that was fixed in 8.01.
不是没有,但我从来没有见过这样的cf8。你确定你安装了最新的修补程序和jvm吗?这可能是在8.08中修复的。
cf8.01的修补程序2
list of all hotfixes and updates for cf8.01
cf8.01的所有修补程序和更新的列表
cf8的修补程序
list of all hotfixes and updates for cf8
cf8的所有修补程序和更新的列表
jvm的升级指令
If you suspect that it's an uncaught exception causing the issue, then might I suggest logging portions of the process. Case in point, I had a similar problem with a scheduled task where it would just bottom out for no reason (never had the reschedule problem though). What I ended up doing to diagnose the problem was use cflog to write out portions of the process as they completed. This particular task too about 4 minutes to complete but ran through about 200 portions (it was a mass emailer for a bunch of clients).
如果您怀疑这是一个未被捕获的异常导致该问题,那么我可以建议记录该过程的部分内容。举个例子,我在预定的任务中遇到了类似的问题,它会毫无理由地触底(尽管没有重新安排问题)。我最终做的诊断问题是使用cflog在完成过程时写出部分过程。这个特殊的任务也需要大约4分钟才能完成,但是已经完成了大约200个部分(这对于一群客户来说是一个大规模的电子邮件)。
I logged the when the portion started and completed along with how log it took. By doing so, i could see what portion would trip up the whole process and knew where to focus my attention.
我记录了部分开始和完成时的记录以及记录的日志。通过这样做,我可以看到哪个部分会绊倒整个过程,并知道在哪里集中我的注意力。
#1
not for nothing, but i've never seen anything like this with cf8. are you sure that you have the latest hotfix and jvm installed? this might have been something in cf8 that was fixed in 8.01.
不是没有,但我从来没有见过这样的cf8。你确定你安装了最新的修补程序和jvm吗?这可能是在8.08中修复的。
cf8.01的修补程序2
list of all hotfixes and updates for cf8.01
cf8.01的所有修补程序和更新的列表
cf8的修补程序
list of all hotfixes and updates for cf8
cf8的所有修补程序和更新的列表
jvm的升级指令
If you suspect that it's an uncaught exception causing the issue, then might I suggest logging portions of the process. Case in point, I had a similar problem with a scheduled task where it would just bottom out for no reason (never had the reschedule problem though). What I ended up doing to diagnose the problem was use cflog to write out portions of the process as they completed. This particular task too about 4 minutes to complete but ran through about 200 portions (it was a mass emailer for a bunch of clients).
如果您怀疑这是一个未被捕获的异常导致该问题,那么我可以建议记录该过程的部分内容。举个例子,我在预定的任务中遇到了类似的问题,它会毫无理由地触底(尽管没有重新安排问题)。我最终做的诊断问题是使用cflog在完成过程时写出部分过程。这个特殊的任务也需要大约4分钟才能完成,但是已经完成了大约200个部分(这对于一群客户来说是一个大规模的电子邮件)。
I logged the when the portion started and completed along with how log it took. By doing so, i could see what portion would trip up the whole process and knew where to focus my attention.
我记录了部分开始和完成时的记录以及记录的日志。通过这样做,我可以看到哪个部分会绊倒整个过程,并知道在哪里集中我的注意力。