FileSystemWatcher + Multiple Events

[Michael Stanbrook]

I'm using the FileSystemWatcher to looks for new files
arriving in a directory. Files are coming in via FTP and
tend to be larger is size (> 1MB at least).

I would like to fire an event once the file is completely
written. I understand there is nothing "exactly" like
that due to how the OS filesystem works, so I am looking
for a workaround.

I am currently attempting to open the "new" file in
exclusing mode to "test" if the file is complete from
within the OnCreate and OnChange event handlers. If the
exclusive open is not successful, I sleep the thread, and
try again. Works like a charm, except I get multiple
Change events thrown, which causes my "test" to be
executed multiple times for each file.

Does anyone have a workaround for this? Perhaps a way to
block/ignore the change events after the first for a
given file?

TIA.

 

[David Sworder]

I'm in the same situation. That FileSystemWatcher is a real pain, isn't it?

The approach I take is similar to yours. I wait for the FileSystemWatcher to
fire an event when the FTP upload begins. I then turn OFF the
FileSystemWatcher and start firing a timer every 10 seconds to see when the
file is completely uploaded. I use the same technique that you do -- try to
open it in exclusive mode. Once the file is completely uploaded, I move the
file to a processing directory, kill the timer, and finally reactivate the
FileSystemWatcher.

David

 

[Mike Stanbrook]

David,

Whew, I thought I was the only one!

Are you actually using a timer? One of the other posts I
found on this topic suggested using a Thread.Sleep(xxx)
instead, and I'm wondering if there is much diference
betwen the two...

Thanks for your input..happy to hear I'm at least on the
right track.

Mike

 

[David Sworder]

Whew, I thought I was the only one!

Are you actually using a timer? One of the other posts I
found on this topic suggested using a Thread.Sleep(xxx)
instead, and I'm wondering if there is much diference
betwen the two...

The vast majority of the time, Thread.Sleep() will work just as well as
a timer and Sleep() is easier to use and makes your code a bit easier to
follow too. The thing is, Sleep() blocks the calling thread. That's what
it's designed to do. In 99% of the cases this is no problem, but in a really
busy server process that is servicing tens of thousands of requests, it's
desirable to minimize the number of blocked threads. You see, the
FileWatcher ultimately fires its event from a "thread pool" thread. These
threads are a very valuable resource. There are only 25 of them per CPU. In
a situation where you have thousands of requests coming into your service
process, you don't want to waste one of your thread pool threads by blocking
(sleeping). Instead, it's better to set the timer and let that "thread pool"
thread return back to the pool so that it can service another request while
you're waiting for the timer to fire.

Unless your designing a high-load server app though, it usually makes
more sense to use Sleep() as you are doing.

David