I'm getting some very strange behavior from my app. The symptom is simple enough: after rebuilding the app or recycling the app pool, IIS starts the app and serves a request successfully, then dies silently (or something -- w3wp still lives). New request equals new app start. Sometimes the app "sticks" after two or more requests, sometimes it just doesn't want to stay alive.
I have no idea if this has anything to do with Windsor, MonoRail or my own components, but when I remove certain startable components the symptom is subtly changed -- fewer or no "restarts" are required to make the app stay alive. When debugging w3wp during app start, I see a lot of exceptions, such as EEFileLoadException and HRException and groups of up to ~80 identical lines saying: "First-chance exception at 0x76d042eb in w3wp.exe: 0xE0434F4D: 0xe0434f4d." I don't know if these exceptions are related to my problem. Any ideas how I should go about finding the root of this evil? I'm tired of having to massage my app into action :). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
