fileset-ftp – repeats processing if file cannot be deleted

[Peter Heggie]

Had a situation today where a file was processed over and over by the inbound thread, for a fileset-ftp, when the file could not be ‘deleted behind’.

I confess I was the culprit – I had the file open in Microsoft Word. So the file was converted to a message and went through the filter and translate, and on out to the outbound thread, about a hundred times.

There are no messages in the error queue. The NetMonitor did show an error on the inbound thread, and the error in the process log was clear enough, but I don’t watch the NetMonitor all day.

I can imagine that anyone with access to the folder/file could do the same thing, and I’m wondering if anyone else has had this problem and how can you detect and recover quickly from this?

Thanks,

Peter

Peter Heggie

Topic

[David Barr]

I usually use Moveit Central for these types of transfers. It’s pretty smart about not reprocessing files that it failed to delete.

[Elisha Gould]

we normally rename the file before reading it using a tclproc.

If the rename fails, then it can be retried on the next scheduled time.

[Charlie Bursell]

You could write a proc, save the last read in a global.  Then if it attempts to read the same file again ignore it and send email to someone to check on it

[Peter Heggie]

thank you everyone. I have some investment in the existing file names and the code for a global variable for the last file read sounds short so I think we will go that way.

Peter Heggie

[Author]

Replies