Unreliability of the FileSystemWatcher
-
I have a system that generates files and writes them to a local directory on the same comuter. The director is mnitored by a FileSysemWatcher that stores the name f the file to a database. The probles is that the FSW, as appeares to be in a completely random manner- sometimes ignores newly created files. If I cut the files to another directory and then manualy copy them back- the event does fire. What can account for such unriliable behavior. Obviously, the monitoring flag is on. Moreover, I doubt that I am having trouble with buffer overflow because I noticed this wiered behavior when not more than 2 or three files were generated. I cannot relocate to db logic to the internals f the system that actually generates the files (It is a C++ library and I dont have the code). Solutions and elegant workarounds would be appreciated. Tahnx. int a; if(a > 0) {...}
-
I have a system that generates files and writes them to a local directory on the same comuter. The director is mnitored by a FileSysemWatcher that stores the name f the file to a database. The probles is that the FSW, as appeares to be in a completely random manner- sometimes ignores newly created files. If I cut the files to another directory and then manualy copy them back- the event does fire. What can account for such unriliable behavior. Obviously, the monitoring flag is on. Moreover, I doubt that I am having trouble with buffer overflow because I noticed this wiered behavior when not more than 2 or three files were generated. I cannot relocate to db logic to the internals f the system that actually generates the files (It is a C++ library and I dont have the code). Solutions and elegant workarounds would be appreciated. Tahnx. int a; if(a > 0) {...}
Hrusha42 wrote:
FSW, as appeares to be in a completely random manner
Do you have any other system processes that is interfering with it?
Vasudevan Deepak Kumar Personal Homepage Tech Gossips
-
I have a system that generates files and writes them to a local directory on the same comuter. The director is mnitored by a FileSysemWatcher that stores the name f the file to a database. The probles is that the FSW, as appeares to be in a completely random manner- sometimes ignores newly created files. If I cut the files to another directory and then manualy copy them back- the event does fire. What can account for such unriliable behavior. Obviously, the monitoring flag is on. Moreover, I doubt that I am having trouble with buffer overflow because I noticed this wiered behavior when not more than 2 or three files were generated. I cannot relocate to db logic to the internals f the system that actually generates the files (It is a C++ library and I dont have the code). Solutions and elegant workarounds would be appreciated. Tahnx. int a; if(a > 0) {...}