[Mono-bugs] [Bug 68854][Cri] Changed - mod_mono returns 503 when using the Apache 2 "worker" MPM

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Tue, 1 Feb 2005 20:54:05 -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 miguel@ximian.com.


--- shadow/68854	2005-01-31 20:12:41.000000000 -0500
+++ shadow/68854.tmp.23802	2005-02-01 20:54:05.000000000 -0500
@@ -107,6 +107,41 @@
 on an equal footing.
 ------- Additional Comments From rlyon@novell.com  2005-01-31 20:12 -------
 Created an attachment (id=13990)
+------- Additional Comments From miguel@ximian.com  2005-02-01 20:54 -------
+We discussed this problem today, and the problem with mod_simias
+as is stands right now is that it interacts badly with the ASP.NET
+The problems compound like this:
+* We need to deliver the unload event (we did not in the past, but
+  we implemented this at the request of the Simias/iFolder group).
+* The unload event is delivered: 
+     a) pre-fork mode: automatically, by sending a special message
+        to mod-mono-server.
+     b) worker mode: when using the --terminate command line argument.
+  In worker mode it is not possible to use the automatic message,
+because Apache processes are quickly recycled.  If we used this in
+worker mode Mono would be constantly recompiling the code every time
+one of the workers was recycled and the module shut down.
+* The "worker" mode will manage to start up a bunch of different
+  mod-mono-server.exe but any process can terminate it.  So it
+  can be started from process 1, and terminated by process 2.
+* This is why we suggested that if you want to use this model, you
+  must manually shut down mod-mono-server with the --terminate 
+  option from your scripts.
+An explanation of what is the workaround that you had in mind
+with mod_simias is would be useful.
+We have very a bad feeling about this mod_simias.