[Mono-bugs] [Bug 79361][Wis] New - [XSP] Exception when stoping Mono.WebServer.ApplicationServer

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Mon Sep 11 14:33:53 EDT 2006


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 jfburdet at humanweb.ch.

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

--- shadow/79361	2006-09-11 14:33:53.000000000 -0400
+++ shadow/79361.tmp.31079	2006-09-11 14:33:53.000000000 -0400
@@ -0,0 +1,63 @@
+Bug#: 79361
+Product: Mono: Tools
+Version: 1.1
+OS: 
+OS Details: XP SP2 / Visual Studio 2005
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: XSP
+AssignedTo: gonzalo at ximian.com                            
+ReportedBy: jfburdet at humanweb.ch               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: [XSP] Exception when stoping Mono.WebServer.ApplicationServer
+
+Description of Problem:
+
+XSP is launching Mono.WebServer.ApplicationServer, but when the thread is 
+stopped, an ObjectDisposed exception is thrown from OnAccept (IAsyncResult 
+ares)
+
+Steps to reproduce the problem:
+1. Start XSP
+2. Hit enter in the console to stop it
+
+Actual Results:
+- an exception is launced
+
+Expected Results:
+- XSP should stops quietly
+
+How often does this happen? 
+- every time
+
+Additional Information:
+- I believe that that problem could be solved by adding a inner try/catch 
+in the finally block because like : 
+
+void OnAccept (IAsyncResult ares)
+		{
+			Socket accepted = null;
+			try {
+				accepted = listen_socket.EndAccept (ares);
+			} catch {
+			} finally {
+                try
+                {
+                    listen_socket.BeginAccept(accept_cb, null);
+                }
+                catch (ObjectDisposedException) { }
+            }
+
+			if (accepted == null)
+				return;
+			accepted.Blocking = true;
+			SetSocketOptions (accepted);
+			StartRequest (accepted, 0);
+		}
+
+Since I'm not an expert, this should be confirmed by a Mono dev.


More information about the mono-bugs mailing list