David
Mon Oct 31 17:51:45 CST 2005
My blog entry is about diagnosing crashes on IIS6, but it is generic enough
to apply conceptually:
http://blogs.msdn.com/david.wang/archive/2005/08/29/HOWTO_Understand_and_Diagnose_an_AppPool_Crash.aspx
> I want to know the couses of this problem, so that I can narrow it
> down a little bit.
Other than intuition, the only sure way to figure out the causes of this
problem is to debug it. You want to either get comfortable with attaching a
debugger to debug the issue, or use free tools provided by Microsoft, like
IIS State or DebugDiag, to help identify the issue.
> This 503 error seems happened ramdomly, any functions in the fasd.dll
> could give error. The trafic on the server is very low, and no infinitly
loop
> firing URL as I can see. I just don't understand that how come it works
> after a restart of IIS and keep working for almost 4 days, and then
> suddently crash.
Here is a theory: Maybe the ISAPI slowly corrupts heap memory in the process
that it runs in, so that after 4 days enough corruption happens such that
the process finally falls over and causes a noticeable 503 response.
Restarting IIS will reset the dllhost.exe process and obviously clean things
up... until the ISAPI slowly corrupts memory again.
In other words, just because the ISAPI code was reviewed and you see the
problem disappear after restarting IIS, does not mean that the ISAPI is not
the problem. Debugging the issue will clarify which is which. And since the
ISAPI is the one that changed, not IIS, it is more likely that the ISAPI
changes introduced some long-running memory corruption than IIS all of a
sudden starting to corrupt memory slowly.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Zzz" <Zzz@discussions.microsoft.com> wrote in message
news:E7D01B7E-ED19-4ACA-870D-8A61F7B83456@microsoft.com...
Hello David Wang
This ISAPI was developed in house. I have talk to those people who had
worked on it, and checked their code. I could not found any problems at this
time.
I want to know the couses of this problem, so that I can narrow it down a
little bit.
This 503 error seems happened ramdomly, any functions in the fasd.dll could
give error. The trafic on the server is very low, and no infinitly loop
firing URL as I can see. I just don't understand that how come it works
after
a restart of IIS and keep working for almost 4 days, and then suddently
crash.
Those URL with 503 errors. if I type them in my browser and hit enter, they
are all
working find.
Please help, I am doomed.
Thank you
"David Wang [Msft]" wrote:
> This looks to be a problem with /poms/dll/FASD.dll - presumably the ISAPI
> web application that you recently upgraded. You need to start your
> investigations with the product support team of that ISAPI DLL since you
> said you never saw problems before the upgrade.
>
> --
> //David
> IIS
>
http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> //
> "Zzz" <Zzz@discussions.microsoft.com> wrote in message
> news:2D43954D-F7B0-4DF5-9027-A843564EB1BE@microsoft.com...
> Problem:
> When client lunchs browser to our web application's Java applet login
page.
> The applet won't show up. It always says loading applet.
>
> Logs from the IIS log( W3C Extended Log File Format)
>
>
> 2005-10-31 01:57:09 128.1.10.9 - 128.1.10.50 443 GET /poms/dll/FASD.dll
>
GetSystemParameterValue?DocumentType=PharmacyOrder&Parameter=RoutingControlO
> ut-of-process+ISAPI+extension+request+failed.
> 503 Mozilla/4.0+(Windows+XP+5.1)+Java/1.5.0_04
> 2005-10-31 01:57:09 128.1.10.32 - 128.1.10.50 443 GET /poms/dll/FASD.dll
>
GetSystemParameterValue?DocumentType=PharmacyOrder&Parameter=RoutingControlO
> ut-of-process+ISAPI+extension+request+failed.
> 503 Mozilla/4.0+(Windows+XP+5.1)+Java/1.5.0_04
> 2005-10-31 01:57:09 128.1.10.32 - 128.1.10.50 443 GET /poms/dll/FASD.dll
> GetAllTags?ConXNID=Out-of-process+ISAPI+extension+request+failed. 503
> Mozilla/4.0+(Windows+XP+5.1)+Java/1.5.0_04
>
> This 503 error seems cannot recover by itself. Every time client refresh
the
> login page, when it reach the applet part, it shows the same 503 error.
All
> I
> have to do
> is to restart the IIS service, and then every thing is okay. Usually it
> happens every 4 days of normal operations on the web application.
>
> We are running Windows 2000 Server (IIS 5.0) with MS SQL 2000 installed.
> Application protection set to High(isolated). Just recently we upgrade our
> ISAPI web application and installed the new SQL reporting service. Before
> those upgrade, we have never seem this kind of problem before.
>
> Can somebody help me with this issure? What is the couse of it ?
> Please this is urgent. Thank you very much
>
>
>
>
>