FileSystemWatcher fails

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Rob Oldfield - 20 Jan 2005 23:25 GMT

I have an app (that should really be a service, but I haven't got round to
it yet) that just monitors a network folder via a filesystemwatcher for new
files and then does its thing. Generally, it works fine, but it fails about
once a month - which is about one every 2-3 hundred files. No error message
or exceptions... it just fails to notice that the file has appeared. After
that, any other new files are also ignored.

I'm thinking of switching to a dir function running every ten seconds or
so....but was wondering if anyone had any ideas about the situation.

Reply to this Message

Nathan - 21 Jan 2005 03:13 GMT

Hi Rob,
Are you subscribing to the Error Event? Per the docs it sounds like an
internal buffer overflow which won't raise an excpetion but will raise the
FileSystemWatcher.Error Event. If the Error event is never being raised I'd
still play with the InternalBufferSize property to see if it has any affect.

You may also be able to get a dump when notifications stop and hunt down the
internal buffer to see if it's full or not just to verify whether or not this
is the case.

HTH,
Nathan

> I have an app (that should really be a service, but I haven't got round to
> it yet) that just monitors a network folder via a filesystemwatcher for new
[quoted text clipped - 5 lines]
> I'm thinking of switching to a dir function running every ten seconds or
> so....but was wondering if anyone had any ideas about the situation.

Reply to this Message

Rob Oldfield - 21 Jan 2005 09:14 GMT

Thanks for that. I haven't touched the error event so I'll give it a go.

> Hi Rob,
> Are you subscribing to the Error Event? Per the docs it sounds like an
[quoted text clipped - 18 lines]
> > I'm thinking of switching to a dir function running every ten seconds or
> > so....but was wondering if anyone had any ideas about the situation.

Reply to this Message

FileSystemWatcher fails

Free Magazines