David
Tue May 25 02:49:16 CDT 2004
Do your ASP.Net use any sort of shared state or objects that persist across
a recycle?
It sounds like you are using such persisted state -- otherwise, every single
recycle should be have like the other.
At this point, this is no longer an IIS issue but one with your
application's interaction with recycling.
What Middle Tier services is being shared? Are you sure that the app isn't
inadvertently taking some lock in the middle tier services that gets "lost"
by the recycle, and hence on restart "hangs" while waiting for the lock...
When you next see the hang, can you run IIS State on the w3wp.exe in
question and post the log? That way, we can see what is going on inside
that process and see if anything is waiting indefinitely (i.e. "hanging").
http://www.iisfaq.com/default.aspx?view=P197
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Pigglet187" <anonymous@discussions.microsoft.com> wrote in message
news:6E01562B-73E7-40A0-B4B0-826BF5AF1B5E@microsoft.com...
We have some fears on memory consumption if we were to allow no idle
timeout.
To do it we would definately have to increase the currently installed RAM.
If you mean having recycle by a Memory limit, these sites show no sign of a
memory leak and are recycled twice daily automatically, just in case we
don't catch this restart issue.
This is occuring with Multiple ASP.Net applications, all applications on
these machines are basically copies of each other, with cosmetic differences
in their output and data is all coming from the same Middle Tier services.
Each application Runs in its own App pool to protect each clients integrity.
At the time of the "Hang" all requests to that app pool are affected.
Recycling the app pool has only positive effects on these sites.
The problem shows up when they try to come back from being Shutdown by the
idle timout.
They do this multiple times a day without a hitch, except for every so many
restarts.
The hanging application consumes little RAM by the standards of these
applications.
I caught one application immediately after the first failed connection.
Worker Process was using about 6.5 MB
I connected to it a few more times.
Each connection raised the Ram usage on the WorkerProcess about 20K, and
Incremented "Current Anonymous Users" perf counter under Web Service by 1.
Which never decreased on its own.
After waiting 2 minutes for page to load. Closed Browser.
Browser Close Logs this in HTTPError.log
2004-05-25 02:11:08 10.10.50.38 2945 192.168.1.104 80 HTTP/1.1 GET / -
1905456688 Connection_Dropped