A
Antonio Iglesias
I have a webservice that has to make a heavy calculation. We want to use
all the processors the machine has. We have built a multithreaded lib that
will do the calculation. When debugging in a regular exe everything works
fine. But when I call the lib from the webservice, although it works, after
finishing the calculation the threads don't seem to join the current
process. They seem to stay. If I try to debug again I can still see the
threads of the last calculation, and after the 3rd calc, I can see 3 sets of
threads (the whole thread pool is kept).
Is it advisable to spawn new threads from dlls running under IIS?? If it
is, how should I do it so that they will interact happily with IIS?
Regards,
Antonio.
all the processors the machine has. We have built a multithreaded lib that
will do the calculation. When debugging in a regular exe everything works
fine. But when I call the lib from the webservice, although it works, after
finishing the calculation the threads don't seem to join the current
process. They seem to stay. If I try to debug again I can still see the
threads of the last calculation, and after the 3rd calc, I can see 3 sets of
threads (the whole thread pool is kept).
Is it advisable to spawn new threads from dlls running under IIS?? If it
is, how should I do it so that they will interact happily with IIS?
Regards,
Antonio.