[Mono-bugs] [Bug 75455][Nor] New - Slow response from web services under 1.1.8

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Sun Jul 3 15:50:27 EDT 2005

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 sgb at manx.net.


--- shadow/75455	2005-07-03 15:50:27.000000000 -0400
+++ shadow/75455.tmp.17288	2005-07-03 15:50:27.000000000 -0400
@@ -0,0 +1,71 @@
+Bug#: 75455
+Product: Mono: Class Libraries
+Version: 1.0
+OS: Red Hat 9.0
+OS Details: 
+Status: NEW   
+Priority: Normal
+Component: Sys.Web.Services
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: sgb at manx.net               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: Slow response from web services under 1.1.8
+Description of Problem:
+Web services that worked fine with mono 1.1.7 now take 15 seconds to respond with mono 
+1.1.8.  The problem occurs with mod_mono 1.0.9 but not when calling xsp direct.  I can 
+reproduce the problem with the standard xsp examples on Red Hat 9, Debian (Woody) and Mac 
+OS X.
+Steps to reproduce the problem:
+1. Set up mod_mono under Apache and map /test to the xsp examples at e.g. /usr/local/share/
+2. Call the echo function of TestService.asmx, e.g. in a web browser:  http://localhost/test/1.1/
+Actual Results:
+The call returns the expected xml, but takes 15 seconds.  Under mono 1.1.7 the response was 
+immediate.  Running xsp directly instead of mod_mono, the response is immediate.  Firefox and 
+wget don't complain, but curl gives an error message:
+curl http://localhost/test/1.1/webservice/TestService.asmx/Echo?a=test
+<?xml version="1.0" encoding="utf-8"?>
+curl: (18) transfer closed with outstanding read data remaining
+<string xmlns="http://tempuri.org/">test</string>
+Could it be related to keep-alive?  I notice from the response headers that the keep-alive timeout 
+is 15 seconds.  xsp doesn't seem to do keep-alive.  I also notice the value of the Content-Length 
+header is different with mono 1.1.7 than 1.1.8; I think under 1.1.7 it was 95 and under 1.1.8 it 
+was 100; it may be relevant given the curl error message.
+---xsp response headers---
+Server: Mono-XSP Server/ Unix
+Connection: Close
+X-Powered-By: Mono
+Date: Sun, 3 Jul 2005 11:23:46 GMT
+Content-Type: text/xml; charset=utf-8
+---mod_mono response headers---
+Server: Apache/1.3.33 (Darwin) mod_mono/1.0.9 PHP/4.3.11
+X-Powered-By: Mono
+Transfer-Encoding: chunked
+Keep-Alive: timeout=15, max=99
+Connection: Keep-Alive
+Content-Type: text/xml; charset=utf-8
+Expected Results:
+It should return immediately and with no error in curl.
+How often does this happen? 
+Additional Information:
+Tested under Apache 2 on Debian (Woody) and Red Hat 9, Apache 1.3 on Mac OS X.  Used mono 
+1.1.8 and with source and binary distributions.  mod_mono and xsp are both version 

More information about the mono-bugs mailing list