Well, I have my nice Mutex based resource locking class which seems to work well, even when being hammered by different threads repeatedly locking and unlocking the same Mutex.

There is a problem though, ASP isn't behaving in the multi-threaded nature I expect it to.

If I manually lock the mutex externally from my test app and then load an ASP page that waits for the mutex to be released it blocks all ASP processing for the website until the mutex is released or it times out. I expected other ASP threads to continue processing page requests, even if one was blocked waiting for the lock. This isn't happening, even when an ASP page is requested from a completely separate client machine.