Re: IIS 6 SLOW response. Reboot needed.
From: Ruben N (rubendn_at_nospam.com)
Date: 05/05/04
- Next message: CreativeONE: "Re: IIS 5.1 -XP =localhost prompts for username and password?"
- Previous message: Ruben N: "Re: ASP.DLL Hangs"
- In reply to: David Wang [Msft]: "Re: IIS 6 SLOW response. Reboot needed."
- Next in thread: Ron: "Re: IIS 6 SLOW response. Reboot needed."
- Reply: Ron: "Re: IIS 6 SLOW response. Reboot needed."
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 5 May 2004 08:15:01 -0400
Ron,
This is what happened to us:
Moved over a few websites that use Access to a brand new more powerful W2K3
server from a W2K server. These websites had functioned flawlessly for a
couple of years.
After the move, after periods of time (ranging from 10 minutes to 2 hours)
the server would stop serving ASP pages and would only serve static pages
until it was restarted.
I was getting the following error in the Application log:
"ISAPI 'C:\WINDOWS\system32\inetsrv\asp.dll' reported itself as unhealthy
for the following reason: 'ASP unhealthy because 100% of executing requests
are hung and 36% of the request queue is full.'."
I paid for a support incident with Microsoft and after a few days of them
looking at the dumps they sent me a BETA version of a fix to the MS Jet.
The file is a beta fixed msjtes40.dll. The server has been functioning fine
now for about 24 hours.
"David Wang [Msft]" <someone@online.microsoft.com> wrote in message
news:%23%23RrOnoMEHA.1388@TK2MSFTNGP09.phx.gbl...
> If the database connections are via Access, then it is likely to be the
> known Jet DB bug on WS03. Google should turn up results as it is
frequently
> reported.
>
> The other common slow response comes from unbuffered responses from ASP,
> frequently loops that use Response.Flush(). The fixes are in HTTP.SYS and
> will be released as a part of SP1.
>
> If you use IIS State ( http://www.iisfaq.com/default.aspx?view=P197 ) to
> capture state inside a w3wp.exe when the ASP pages with database
connections
> are performing poorly, it can be verified as to what's your cause.
>
> You should never need to reboot the server on IIS6. Only need to recycle
> the Application Pool, which is equivalent to running IISRESET or
restarting
> IIS. Recycle the Application Pool basically brings up a brand new worker
> process to handle new requests while the old one drains its existing
> requests (and killed if it doesn't finish them fast enough). Basically
what
> IISRESET or restarting IIS does, except it's better in that connections
are
> not dropped.
>
> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> //
> "Ron" <r.van.engelen@global-e.nl> wrote in message
> news:a0c3fb38.0405042313.4273600d@posting.google.com...
> Recently we have installed a Windows 2003 IIS 6 machine. Currently
> about 100 websites are running on this machine. Many of the websites
> have moved from an older IIS 5 machine.
>
> We now have the problem that these websites (.ASP pages with database
> connections) are performing very very slow sometimes. At times the
> dynamic sites do not respond at all but the basic static (html) sites
> are still being services. A full reboot of the server is then
> required. I NEVER had this problem on IIS 5.
>
> Somewhere here on Google I found that I should add a parameter for ASP
> in the register. I had to set the VALUE
> "DisableLazyContentPropagation" to 1. This doesn't seem to solve my
> problem.
>
> Can anybody help me to find a solution for this IIS 6 behaviour.
>
>
- Next message: CreativeONE: "Re: IIS 5.1 -XP =localhost prompts for username and password?"
- Previous message: Ruben N: "Re: ASP.DLL Hangs"
- In reply to: David Wang [Msft]: "Re: IIS 6 SLOW response. Reboot needed."
- Next in thread: Ron: "Re: IIS 6 SLOW response. Reboot needed."
- Reply: Ron: "Re: IIS 6 SLOW response. Reboot needed."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|