IIS App Pool Crash

[Cantor, Scott]

On 10/28/11 12:04 PM, "Joe Lawson" <jlawson at weaveonline.com> wrote:
>
>The application event below is recorded right before the Access
>Application crash.   I've also went back to Microsoft for help in
>analzying the problem and they still indicate that it appears the problem
>lies with the Shibboleth component.

Something that is supposed to be set for every request by IIS is
apparently not set. My logging is unfortunately not sufficient in that
release to tell which piece of information it is, but the set of
possibilities is small.

When my code throws that particular exception, I log it (what you saw) and
then I tell IIS to send back a response to the client with the same error
message. At least when I last tested that error path, it worked fine.

Here, IIS is shutting down my filter and probably unloading it from
memory. But it also lets the call into the IIS server support function to
send the response to the client proceed. When that happens, the static
string constant I passed into the function is gone from memory by the time
the call happens.

I claim that's a bug. IIS can't unload me and then still run my exception
handler.

What I do want is to try and reproduce the crash itself if I can find out
what exact version of IIS you're using. Please file a bug and attach your
details and the original stack trace they gave you.

If I can't make progress that way, I may need you to drop in a patched DLL
to add some logging, since you're apparently able to crash it. We can
coordinate that via the bug report.

-- Scott