calling ThreadPool.SetMaxThread in ASP.NET

[Fowad]

I am using ThreadPool to generate multiple threads in my Web Service. Web
methods call ThreadPool.QueueUserWorkItem and then wait for the response
using Monitor.Wait.

All of this works, unless I call SetMaxThreads in the constructor. In this
case, the first call goes through but it hangs the process. Subsequent calls
get no response from the web service.

SetMinThreads seems to cause no problems though. Any idea

 

[John Saunders [MVP]]

I am using ThreadPool to generate multiple threads in my Web Service. Web
methods call ThreadPool.QueueUserWorkItem and then wait for the response
using Monitor.Wait.

All of this works, unless I call SetMaxThreads in the constructor. In this
case, the first call goes through but it hangs the process. Subsequent
calls
get no response from the web service.

SetMinThreads seems to cause no problems though. Any idea

I don't know the exact answer, but in general, a web service shouldn't need
to screw around with thread pool settings.

Also, were you aware that your web service requests arrive on a thread pool
thread, and while your service is waiting for the worker thread to complete,
you service is holding on to the thread pool thread? This prevents it from
being used by other requests.