[Mono-bugs] [Bug 52169][Cri] New - WebServices Problem

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Thu, 8 Jan 2004 11:00:19 -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 lluis@ximian.com.

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

--- shadow/52169	2004-01-08 11:00:19.000000000 -0500
+++ shadow/52169.tmp.24811	2004-01-08 11:00:19.000000000 -0500
@@ -0,0 +1,44 @@
+Bug#: 52169
+Product: Mono/Runtime
+Version: unspecified
+OS: Red Hat 9.0
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: Unknown
+Priority: Critical
+Component: misc
+AssignedTo: lluis@ximian.com                            
+ReportedBy: shiziye@hotmail.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: WebServices Problem
+
+I have found that XSP-0.6 is very unreliable on RedHat 9.
+But I thought this is the problem of XSP before.
+Now, I successfully run XSP-0.6 on Windows 2003.
+And it is much more reliable then on RedHat 9.
+
+I just write a program that continue to access the same webservice provide
+in different evironment with 10 thread, and use it to test webservice
+provider. The webservice is simple, just add two string and return the
+result. I run webservice project in these evironment.
+1. IIS on Windows 2003
+  Program run with the best performance and no problem found. 
+2. XSP-0.6 on Windows 2003
+  Program can run with low performance. And after a few minutes, all the
+memory been used, connection closed, and program throw exception.
+3. XSP-0.6 on RedHat 9
+  Program can not run at all.
+
+I don't know if it's the problem of runtime or the problem of ClassLibrary.
+But I know now that it is not only the proble of XSP-0.6.
+
+------- Additional Comments From lluis@ximian.com  2003-12-16 05:33 -------
+It would be very helpful if you can attach the test program and test
+web service.
+
+------- Additional Comments From gonzalo@ximian.com  2003-12-17 20:39 -------
+*** Bug 52170 has been marked as a duplicate of this bug. ***