>What was the suggested workaround ?

Application.Lock()
oDataAdapter.Fill(oDataSet)
Application.UnLock()

You will see that instead of having several errors per seconds, you will get only several errors per minutes. The environment for the testing that person used was not having an intensive SQL command. If you test it with about 10 tables as far as the INNER JOIN goes within the same SQL with a lot of fields, this does not resolve the issue.

When using that, he mentioned that this would limit the scalability. He found that one can improve the scalability to a great extent by configuring the IIS6 Application Pool, Performance tab property "Maximum number of worker processes" to a number greater than the default of 1, to something between 3 and 6.

But, still, having to lock the application 40 times in one hit and about 160 times per seconds, assuming 4 hits a second, is, of course, a workaround that wouldn't make sense for me to use.