[Mono-bugs] [Bug 71662][Nor] New - XSP: Accessibility to Session in Session_Ends (global.asax)

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Mon, 24 Jan 2005 05:17:33 -0500 (EST)


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 aanfray@perinfo.com.

http://bugzilla.ximian.com/show_bug.cgi?id=71662

--- shadow/71662	2005-01-24 05:17:33.000000000 -0500
+++ shadow/71662.tmp.11486	2005-01-24 05:17:33.000000000 -0500
@@ -0,0 +1,59 @@
+Bug#: 71662
+Product: Mono: Tools
+Version: 1.1
+OS: Red Hat 7.3
+OS Details: Mono & XSP are 1.0.5
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: XSP
+AssignedTo: gonzalo@ximian.com                            
+ReportedBy: aanfray@perinfo.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: XSP: Accessibility to Session in Session_Ends (global.asax)
+
+Description of Problem:
+The Session object is *sometimes* accessible in Session_Ends function of
+global.asax.
+
+
+Steps to reproduce the problem:
+1. Use the test case provided (global.asax, web.config, default.aspx)
+2. Put a value in the TextBox, wait the Session_Ends is triggered and
+see the results in the terminal in which you started XSP server
+(the results are output there) 
+
+Actual Results:
+Listening on port: 9090
+Listening on address: 0.0.0.0
+Root directory: /home/aanfray/test_session
+Session starts (09:32:38) ID=6B470FA69680E5919A3C930BD22100
+Error:Failed to get session object
+Session starts (09:37:08) ID=D2E657EBDA2001B2AE4AFE7DEB00A0
+Error:Failed to get session object
+
+Expected Results:
+Session starts (09:32:38) ID=6B470FA69680E5919A3C930BD22100
+foo="the value you entered"
+Session ends (09:34:42) ID=6B470FA69680E5919A3C930BD22100
+
+How often does this happen? 
+Not always but quite often (that's bad)
+
+Additional Information:
+I also tried with several browsers at the same time (to create different
+session). It doesn't work better, and when it doesn't simply failed, it
+produce bad results such as:
+
+Session starts (10:12:22) ID=966FE786E1DAC7FDF8CAB6D2BB2064
+Session starts (10:12:35) ID=C492056064D5C5ADBAF86BDA76E920
+foo=toto
+Session ends (10:14:26) ID=C492056064D5C5ADBAF86BDA76E920
+foo=toto
+Session ends (10:14:42) ID=C492056064D5C5ADBAF86BDA76E920
+
+As far as I can understand, it has mixed the Session objects...