(In this post, I use the terms "fail" and "hang" interchangeably, and
they mean that the process isn't closing down when it should. Read on!)
Hey everyone,
I posted a while back about certain ISAPI dlls hanging in IIS. By
hanging, I mean the process isn't getting killed after the idle time is
gone. It has to go to the 29 hour app. pool recycle to get rid of the
process (IIS does, that is). This is still happening. We pulled the
network cable, as suggested, and that doesn't seem to help. The process
runs for the 29 hours. I'd like to fix this problem soon because of
deadlines.
One thing I noticed is that it doesn't happen to all of our dlls. It
only happens with specific ones. I have tried and tried to get one to
fail, but I can't seem to, whereas these two others will fail when I
run long load tests on them, and another one will fail even with small
tests, it seems. That's why I was wondering if there could be anything
with the dlls themselves that is causing this problem.
Any clue as to why these dlls would be doing this, and any way that we
might be able to get around it if we can't fix it? Thanks.
Kyle
FAQ
Profile
Private Messages
Log in
