IIS 5.0 Leak or Inetmon 3.1 bug?
Egbert Nierop
I have found a severe leak. My post before was about the same and I found
some leaks in using ADO methods that have been solved by working around.
The ONLY leak that leaves is this '100% REPROducable one'!
step 1) have Inet mon 3.1 installed on another system (from the backoffice
resource kit)
step 2) make a simple ASP page containing nothing but this
<%
Response.Write "<HTML>hello world</HTML>"
%>
step 3) make a inetmon script that contains this
POST url:/yoursimpleasp.asp?properties:x=1
SLEEP 300
step 4) set inetmon to simulate some 20 clients and have 20 worker threads
and set cookies to runtime
step 5) run it all. You'll notice two things a) sessions run up very fast b)
your memory does leak and you'll NEVER get it back even if ALL sessions
expire!
My suspect is that or Inetmon does not handle the sessionid cookie right or
that IIS just can't handle the type of post inetmon uses. IIS SHOULD give
back all the memory when sessions expire or the unload feature is used.
That's it.
Egbert Nierop