[Mono-bugs] [Bug 68854][Cri] Changed - mod_mono returns 503 error on web service request when using apache2 worker mpm

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Tue, 9 Nov 2004 13:20:27 -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 mlasky@novell.com.

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

--- shadow/68854	2004-11-08 18:47:45.000000000 -0500
+++ shadow/68854.tmp.30891	2004-11-09 13:20:27.000000000 -0500
@@ -1,13 +1,13 @@
 Bug#: 68854
 Product: Mono: Class Libraries
 Version: unspecified
 OS: SLES 9
 OS Details: 
-Status: RESOLVED   
-Resolution: WONTFIX
+Status: REOPENED   
+Resolution: 
 Severity: Unknown
 Priority: Critical
 Component: Sys.Web
 AssignedTo: gonzalo@ximian.com                            
 ReportedBy: mlasky@novell.com               
 QAContact: mono-bugs@ximian.com
@@ -61,6 +61,21 @@
 
 ------- Additional Comments From gonzalo@ximian.com  2004-11-08 18:47 -------
 Workaround is to start/stop mod-mono-server in the same script as
 apache and pass the 'MonoRunXSP false' directive to apache.
 
 I will add a --kill option to mod-mono-server tomorrow.
+
+------- Additional Comments From mlasky@novell.com  2004-11-09 13:20 -------
+While I agree with this fix as a work around, I think that 
+additional work should be considered to not have to modify the 
+apache startup script to run mod-mono-server. Every application that 
+depends on mod-mono-server will then have to do this same install 
+work and might conflict with another application's installation.
+
+It might be good to consider turning mod-mono-server into a daemon 
+so that it could be stopped and started on its own and not rely on 
+being put in the apache startup script. That way all applications 
+that depend on mod-mono-server could start and stop it in the same 
+way.
+
+Just my thoughts.