BorlandTalk.com

[Brian]

Hello all,

I currently have an ISAPI dll in development that has been running
pretty well for about 6 months (with major revisions every once in a
while). Anyhow I'm trying to get a better understanding of the ISAPI
dll, threads, and the threads that each one of those threads spawn.
More importantly, how this affects performance.

I notice that when the DLL is loaded and first called a seperate
DLLHOST process appears in windows server task manager. Right off the
bat it has 40 threads. I assume some of these are worker threads.
However I've never been able to nail down why the thread count is 40.
It may be something elementary to how windows manages threaded
applications but I'm still curious.

Each call to the DLL can spawn up to 6 other threads (which I manage
from within the application). These threads get terminated internally
when they complete. However sometimes we have to terminate the threads
outside the normal thread handler. We find sometimes that when this
happens in frequent succession our application just dies. Basically
what will happen at this point is that it stops actually accepting
connection...yet the thread count in the task manager increases as does
the memory used. At this point I can only kill the process and reload
the DLL. Again this doesn't happen often but enough to make me want to
figure out why.

Could someone point me in the direction of a good resource where I
could read up on threads in ISAPI dll's etc?

Thanks in advance
-Brian

[Riki Wiki]

On 2 Mar 2006 08:18:26 -0800, Brian wrote: