Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=82193 --- shadow/82193 2007-07-26 12:25:15.000000000 -0400 +++ shadow/82193.tmp.23729 2007-07-26 17:42:02.000000000 -0400 @@ -127,6 +127,28 @@ EXCEPTION handling: TypeLoadException EXCEPTION handling: NullReferenceException EXCEPTION handling: NullReferenceException The TypeLoadException looks a bit fishy to me.... + +------- Additional Comments From [EMAIL PROTECTED] 2007-07-26 17:42 ------- +Forget about the TypeLoadException. Generating a trace like this gives +more insight: + +mono +--trace=N:System.Web.SessionState,M:System.Web.HttpContext:get_Session,M:System.Web.HttpContext:SetSession + /usr/local/lib/mono/2.0/xsp2.exe + +The bug is in method SessionStateModule.OnAcquireRequestState. At the +time of the first request, we have (storeData == null). +"handler.CreateNewStoreData" (SessionInProcHandler.CreateNewStoreData) +is called which in turn calls +"SessionStateUtility.GetSessionStaticObjects(context)". Inside this +method we have (context.Session == null), so it returns null. + +In the end, "SessionStateUtility.AddHttpSessionStateToContext" is +called (which requires (context.Session == null!)), which sets +context.Session... + +The ordering is wrong. "SessionStateUtility.GetSessionStaticObjects" +depends on context.Session already being set! _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
