HttpWebRequest and ThreadPool
ASP.NET
1
Posts
1
Posters
0
Views
1
Watching
-
I am calling a .NET web service from within a COM+ application component invoked from an ASP page. After some calls I get the following error "There were not enough free threads in the ThreadPool object to complete the operation.". I understand that by default they are only 25 thread per CPU available but when the system is under load why are the requests not queued. I was under the impression that this was one of the many advantages of using threadpooling! I have read the two MS articles on this () and I cant believe that this is by design. Surely you must be able to make multiple calls to web services without implementing your own queuing or throttling. I need to ship our product within the week. PLEASE HELP! ANYTHING CONSIDERED!