IIS App Pool Crash

[Joe Lawson]

Hi Scott,

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.

I would be grateful for an direction on what to check or other ideas.

Thanks,


Log Name:      Application
Source:        Shibboleth ISAPI Filter
Date:          10/28/2011 10:12:29 AM
Event ID:      2100
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      XX
Description:
The description for Event ID 2100 from source Shibboleth ISAPI Filter cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event: 
A required variable or header was empty.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Shibboleth ISAPI Filter" />
    <EventID Qualifiers="0">2100</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-10-28T14:12:29.000000000Z" />
    <EventRecordID>90597</EventRecordID>
    <Channel>Application</Channel>
    <Computer>XX</Computer>
    <Security />
  </System>
  <EventData>
    <Data>A required variable or header was empty.</Data>
  </EventData>
</Event>

// this from the shibd.log
2011-10-28 10:12:43 INFO Shibboleth.Listener [5]: detected socket closure, shutting down worker thread





________________________________________
From: users-bounces at shibboleth.net [users-bounces at shibboleth.net] On Behalf Of Cantor, Scott [cantor.2 at osu.edu]
Sent: Wednesday, October 26, 2011 12:37 PM
To: users at shibboleth.net
Subject: Re: IIS App Pool Crash

On 10/26/11 12:12 PM, "Joe Lawson" <jlawson at weaveonline.com> wrote:
>
>Is anyone on the list aware of any similar problems or offer any insight
>on what we should do to resolve the problem?

I took a look at the trace, and the sequence of calls doesn't match what
the code is. But there's an exception catch occurring ahead of the end of
the stack that makes me think it's a problem with IIS shutting down the
filter ahead of the exception's handler running inside the filter. That
would be, frankly, a bug in IIS, but I'll reserve judgement for the moment.

I think there should be a Windows event log indication of the filter
recording an exception of some sort. The filter logs something there any
time there's an exception propagated that far. If not, I don't understand
the stack trace, and since I can't reproduce the crash, I can't debug into
it.

Depending on whether there's an event log entry, I may have other ideas.

I think the crash is really about something else, and the trace might just
be a crash during the response to the real problem.

-- Scott

--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net