Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have web application that accepts an uploaded file, writes it to a share, and then sends a message to the middle tier with the name of the file for processing. There have been sporadic errors in the application log saying that the middle tier machine could not find the file. I'm wondering if there is any theoretical lag between when the file has been closed on the front end machine and when it would be acknowledged as existing from the middle tier. It would make sense for the protocol to always try and ask the server directly for a file it has not accessed before, rather than relying on some kind of cached state, but I don't understand the underlying protocol well enough to tell.


share|improve this question
Are you sure it's really not found, or could it be throwing that error if the file is locked/not closed instead of really not found? –  Bart Silverstrim Feb 10 '12 at 17:36
Also, depending on the method used to "find" your files on the other side... it may be relying on cached results and not re-indexing the directory immediately. –  TheCompWiz Feb 10 '12 at 17:42
@Bart The error received is file not found, so not a lock situation. –  jlew Feb 10 '12 at 18:27
@TheCompWiz The code is doing a direct open of the fully-qualified path. It is not enumerating the directory or anything like that. –  jlew Feb 10 '12 at 18:27
@jlew what programming language, what method did you use to "direct open", etc... –  TheCompWiz Feb 10 '12 at 20:09

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.