It looks like all the threads you're creating are MTA threads, but the MSTK transport object is apartment threaded so you'll end up with all the MTA threads blocking waiting on the host STA thread. You need to make the threads you're creating be STA threads.
Cheers Simon On Tue, 11 Jun 2002 11:11:14 -0700, in dotnet you wrote: >All, > >First, I would like to thank everyone for trying to help me resolve this >issue. Its definately appreciated. Its still not fixed, but it is >appreciated. > >Here is what I have so far: > >1. Threads are set to low priority and CPU usage is minimal. I do get one >peak of about 89% usage, but only for a split second and then it drops to >aroudn 5%. > >2. The total time to process 100 requests is actuall near 53 seconds. > >3. The MSSoapLib is a COM library used via the interop and yes, the >project was ported from VB6. I am not sure what the threading model is. I >have searched everywhere to find out, but I cannot find anything that would >tell me. > >4. The threading example creates all the threads in a heartbeat. But, it >seems like the threads are backing up waiting their turn to submit. I >agree with Greg and I suspect is does have something to do with the HTTP >1.1 spec or it could be an interop problem using the COM SOAP library. > >So, this all being said, I like the idea of sockets, but I don't even know >where to start. The SOAP code I sent yesterday is the ported interop code >from VB6. Can anyone help me convert this to sockets or to the .NET >framework? Any links or leads are always appreciated. > >Thanks, > >Jesse Sanders > >You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced >DOTNET, or >subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
