[Mono-bugs] [Bug 67935][Cri] New - XSP and/or the client crash on when web app recycles

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Mon, 11 Oct 2004 01:39:50 -0400 (EDT)


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 diltonm@mccomsoft.com.

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

--- shadow/67935	2004-10-11 01:39:50.000000000 -0400
+++ shadow/67935.tmp.1731	2004-10-11 01:39:50.000000000 -0400
@@ -0,0 +1,113 @@
+Bug#: 67935
+Product: Mono: Runtime
+Version: unspecified
+OS: 
+OS Details: Fedora Core 2
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Critical
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: diltonm@McCOMSoft.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: XSP and/or the client crash on  when web app recycles
+
+Description of Problem:
+
+XSP and/or the client crash when the runtime tries to recycle the app
+domain at the interval specified in the machine.config property httpRuntime
+for executionTimeout.
+
+Steps to reproduce the problem:
+
+1. Install 1.0.2 with XSP
+2. Comment out the two extensions in xsp-1.0.2/tests/web.config because
+accessing with a web browser or ServiceCient.exe fails when XSP can't
+locate the extensions.
+3. Run xsp --port 80.
+4. In another terminal, run mono ./ServiceClient.exe.
+5. ServiceClient begins talking to the TestService and reporting results to
+the term window.
+6. Watch the ServiceClient.exe and/or XSP server both crash more or less at
+the timeout specifed in the /etc/mono/machine.config file which defaults to
+90 seconds IIRC.
+
+
+
+Actual Results:
+
+See item 6 above.
+
+
+Expected Results:
+
+Work continuously with no crashes.
+
+
+How often does this happen? 
+
+100% for me. I also tried adjusting executionTimeout to various levels to
+verify that it is directly related.
+
+
+Additional Information:
+
+Here is what my term window where ServiceClient.exe was running looks like:
+
+The server said that 123 + 456 is = 579
+The server said: hola
+The server said that 123 + 456 is = 579
+The server said: hola
+The server said that 123 + 456 is = 579
+The server said: hola
+The server said that 123 + 456 is = 579
+The server said: hola
+The server said that 123 + 456 is = 579
+The server said: hola
+The server said that 123 + 456 is = 579
+The server said: hola
+The server said that 123 + 456 is = 579
+The server said: hola
+The server said that 123 + 456 is = 579
+The server said: hola
+ 
+Unhandled Exception: System.Net.WebException: The request timed out
+in <0x001a8> System.Net.HttpWebRequest:EndGetResponse (System.IAsyncResult)
+in <0x0006d> System.Net.HttpWebRequest:GetResponse ()
+in <0x00078> System.Web.Services.Protocols.WebClientProtocol:GetWebResponse
+(System.Net.WebRequest)
+ 
+[root@mccom-fedora test]#
+
+And here is what the term window running XSP looks like:
+
+xsp
+Adding applications '/:.'...
+Registering application:
+    Host:          any
+    Port:          any
+    Virtual path:  /
+    Physical path: /root/dev/xsp-1.0.2/test
+Listening on port: 80
+Listening on address: 0.0.0.0
+Root directory: /root/dev/xsp-1.0.2/test
+Hit Return to stop the server.
+** Message: Unknown errno: Interrupted system call
+ 
+System.InvalidOperationException: The process must exit before getting the
+requested information.
+in <0x00075> System.Diagnostics.Process:get_ExitCode ()
+in <0x0004c> (wrapper remoting-invoke-with-check)
+System.Diagnostics.Process:get_ExitCode ()
+in <0x002ad> Mono.CSharp.CSharpCodeCompiler:CompileAssemblyFromFileBatch
+(System.CodeDom.Compiler.CompilerParameters,string[])
+in <0x00047> Mono.CSharp.CSharpCodeCompiler:CompileAssemblyFromFile
+(System.CodeDom.Compiler.CompilerParameters,string)
+in <0x00633>
+System.Xml.Serialization.XmlSerializer:RunSerializerGenerationAux (object)
+in <0x0001b> System.Xml.Serialization.XmlSerializer:RunSerializerGeneration
+(object)