[Mono-bugs] [Bug 73357][Blo] Changed - A stop from mod_mono is aborting mod-mono-server prematurely.

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Thu, 31 Mar 2005 20:03:23 -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 rlyon@novell.com.

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

--- shadow/73357	2005-03-05 19:11:54.000000000 -0500
+++ shadow/73357.tmp.29140	2005-03-31 20:03:23.000000000 -0500
@@ -1,13 +1,13 @@
 Bug#: 73357
 Product: Mono: Tools
 Version: 1.1
 OS: unknown
 OS Details: 
-Status: RESOLVED   
-Resolution: FIXED
+Status: REOPENED   
+Resolution: 
 Severity: Unknown
 Priority: Blocker
 Component: XSP
 AssignedTo: gonzalo@ximian.com                            
 ReportedBy: rlyon@novell.com               
 QAContact: mono-bugs@ximian.com
@@ -56,6 +56,12 @@
  
  			AppHost = null;
 
 ------- Additional Comments From gonzalo@ximian.com  2005-03-05 19:11 -------
 Patch is in SVN.
 Thanks!
+
+------- Additional Comments From rlyon@novell.com  2005-03-31 20:03 -------
+The patch in SVN uses a ThreadPool thread (a background thread), but a
+foreground thread is required to make sure that the real stop is
+called.   Under stress, the mod-mono-server will exit before getting
+to the stop thread. I will attached a patch.