Speculation... moving the file pointer (with SetFilePointer()) is a "bad thing" when done inside a locked region.
Bill > > The only problem with this patch is that it occasionally causes the > WriteFile to block indefinitely and all the other worker threads block on > apr_file_lock waiting for the file lock. I can send several thousand > requests through the server before it hangs. I don't see > anything obviously > wrong here or in apr_file_lock|unlock. Obviously I will not commit this > until we figure out and fix what is causing the WriteFile block. > > I generally see the hang writing to the access log. I did see a > hang writing > to the error log at startup once. > > Bill >