M
mjkahn
Everything runs fine for a while (weeks even), and then IIS stops responding
to (or even logging) requests for ASP pages. HTML pages are served up just
fine.
I'm running Windows 2000 SP4, and IIS 5.0. Windows Update tells me I'm up to
date on patches.
The problem has happened three times on a production server and twice on a
test server. I reproduced the problem on the test server after using the web
stress-test tool--once right after the stress-test finished, and once after
the sessions established by another stress-test run timed out. At least two
of the three times on the production server, though, there hadn't been any
real activity (new or timed-out) in several hours.
There's nothing in the Event Log or W3SVC log. No error messages anywhere
that I can find.
Once the problem starts, the IIS Console may hang. This doesn't happen right
away--once, it doesn't happen for many minutes after the problem started.
Once the problem starts, I can't use "NET STOP" to stop the WWW Publishing
Service. IISreset does clear the problem.
My primary ASP application uses some custom VB 6.0 DLLs, and stores a few
references to them in session variables. Although I know that's not advised
(see the recent thread "Storing objects in Session Variables - exactly why
not?"), I don't think it's the cause of the problem--memory and performance
don't seem to be issues. Before I embark on revising several DLLs and many
ASP pages to not store objects in session variables, I'd like to consider
alternatives, especially since I haven't found any indication that this is
causing the problem.
I'd appreciate any thoughts or suggestions you might have.
Thanks!
MJ.
to (or even logging) requests for ASP pages. HTML pages are served up just
fine.
I'm running Windows 2000 SP4, and IIS 5.0. Windows Update tells me I'm up to
date on patches.
The problem has happened three times on a production server and twice on a
test server. I reproduced the problem on the test server after using the web
stress-test tool--once right after the stress-test finished, and once after
the sessions established by another stress-test run timed out. At least two
of the three times on the production server, though, there hadn't been any
real activity (new or timed-out) in several hours.
There's nothing in the Event Log or W3SVC log. No error messages anywhere
that I can find.
Once the problem starts, the IIS Console may hang. This doesn't happen right
away--once, it doesn't happen for many minutes after the problem started.
Once the problem starts, I can't use "NET STOP" to stop the WWW Publishing
Service. IISreset does clear the problem.
My primary ASP application uses some custom VB 6.0 DLLs, and stores a few
references to them in session variables. Although I know that's not advised
(see the recent thread "Storing objects in Session Variables - exactly why
not?"), I don't think it's the cause of the problem--memory and performance
don't seem to be issues. Before I embark on revising several DLLs and many
ASP pages to not store objects in session variables, I'd like to consider
alternatives, especially since I haven't found any indication that this is
causing the problem.
I'd appreciate any thoughts or suggestions you might have.
Thanks!
MJ.