Each detached job is run by a separate 24x7.exe in order to "Detach" it from the main instance. Apparently some of your jobs hanged, maybe because they took more than 10 minutes to run and then interfered with each other. If you run a program type job you can set the job timeout value to 9 minutes 58 seconds (or less) so that the scheduler can forcibly terminate these jobs if they don’t complete on time. If you run a non-program type job you can split it into 2 jobs: the script job ("worker" job with no schedule) and the program type job ("runner" job) to run the script type job using "24x7.exe /JOB [job id]" command. This way you can also set the timeout in the runner job to kill the worker job. : I have a scheduled job that runs every 10 minutes
: in the 'detached' mode. This morning, after running
: all weekend, I found > 20 instances of 24x7.exe in
: the W2K Task Manager utility. Most instances displayed
: had: 11k memory, 111 handles, and 3 threads. What can
: we do to properly manage these 24x7.exe instances rather
: than manually ending each process? Thanks
|
