You searched for the word(s): userid:756987

More Search Options

RSS Available

• Re: Null Reference Exception in SessionStateModule

  We were able to fix this issue. As it turns out, the problem was caused by our custom IIdentity object we use to track authenticated users. I switched our code to use a static, thread-safe collection and pull authenticated users from this collection instead of the HttpContext.Current.User property. Now, our app does not replace the FormsIdentity object, and we no longer experience an app-pool crash under heavy load, and we can leave the security patch in place.

  Posted to State Management (Forum) by MatthewP on 8/30/2007
  Filed under: app pool crash KB928365