Hi,

we have a job that zip's a complete directory into a single Zip-file.
Sometimes, and i don't know why, the FileZip function fails and create's
~10.000 .tmp files (per try) in the Queue subdirectory. Stopping 24x7 and restarting it
results in a startup time of 5-10 minutes for the scheduler.

Error message says that a certain file could not be added to the archive.
Running the script again (after restarting 24x7) usually works fine.

Today i had over 30.000 (!) .tmp files in the queue directory, try to delete this ...

Someone had an similar problem ?

Alex

How this job is scheduled? Is it a file-watch job? How does it run (synchronous/synchronous/detached)?

PS. I guess 5-10 minutes startup time is the time taking to delete such larger number of .tmp file.

: Hi,

: we have a job that zip's a complete directory into a single Zip-file.
: Sometimes, and i don't know why, the FileZip function fails and create's
: ~10.000 .tmp files (per try) in the Queue subdirectory. Stopping 24x7 and
: restarting it
: results in a startup time of 5-10 minutes for the scheduler.

: Error message says that a certain file could not be added to the archive.
: Running the script again (after restarting 24x7) usually works fine.

: Today i had over 30.000 (!) .tmp files in the queue directory, try to delete
: this ...

: Someone had an similar problem ?

: Alex

: How this job is scheduled? Is it a file-watch job? How does it run
: (synchronous/synchronous/detached)?

: PS. I guess 5-10 minutes startup time is the time taking to delete such
: larger number of .tmp file.

Yes, but i'm not sure the .tmp files are really being deleted by the scheduler ...
I usually delete them manually.

The Job properties are as following:

Job is timer-scheduled every workday between 07 til 15.00.
The JAL script then checks for an additional GO file before start zipping.
Job is synchronous and currently not detached.
Skip-Job is enabled if one minute delay is reached.
It's only one of two jobs in this specific queue.
There's obviously no other job that can interfere (at least in this queue) ...

Scheduler version: 3.4.17
File-System: NTFS (ZIP location), FAT (System Disk & Scheduler location)
OS: Windows NT 4.0 Server

Alex

Try 2 things:

1. As the first statement in the job set the current directory to your system TEMP directory for example

CD "c:\\temp"

2. Set the job to run detached.

: Yes, but i'm not sure the .tmp files are really being deleted by the
: scheduler ...
: I usually delete them manually.

: The Job properties are as following: Job is timer-scheduled every workday
: between 07 til 15.00.
: The JAL script then checks for an additional GO file before start zipping.
: Job is synchronous and currently not detached.
: Skip-Job is enabled if one minute delay is reached.
: It's only one of two jobs in this specific queue.
: There's obviously no other job that can interfere (at least in this queue)
: ...

: Scheduler version: 3.4.17
: File-System: NTFS (ZIP location), FAT (System Disk & Scheduler location)
: OS: Windows NT 4.0 Server

: Alex

: Try 2 things: 1. As the first statement in the job set the current directory
: to your system TEMP directory for example

: CD "c:\\temp"

: 2. Set the job to run detached.

O.K.,

i've done this.
But DETACH means it does not run synchronous anymore, right ?
I've seen several instances of the scheduler when running today.

But besides this, it ran well without problems (at least today) ...

We'll have an eye on it :-)

Alex

"Detached" simply means that the job is run by a separate instance of 24x7 job engine (you can see separate 24x7.exe in the Windows task list). This allows complete separation (detachment) of the job and its child processes from the main job engine.

: O.K.,

: i've done this.
: But DETACH means it does not run synchronous anymore, right ?
: I've seen several instances of the scheduler when running today.

: But besides this, it ran well without problems (at least today) ...

: We'll have an eye on it :-)

: Alex