[Mono-bugs] [Bug 79931][Blo] Changed - [amd64-only] xsp-1.1.18 on mono-1.2 throws random exceptions when serving web services requests

[bugzilla-daemon at bugzilla.ximian.com]

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 jan.oravec at 6com.sk.

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

--- shadow/79931	2006-11-14 14:36:11.000000000 -0500
+++ shadow/79931.tmp.29143	2006-11-21 19:22:18.000000000 -0500
@@ -1,23 +1,23 @@
 Bug#: 79931
-Product: Mono: Class Libraries
-Version: 1.1
-OS: 
-OS Details: Gentoo
+Product: Mono: Runtime
+Version: 1.2
+OS: GNU/Linux [Other]
+OS Details: Gentoo, amd64
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Blocker
-Component: CORLIB
+Component: interop
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: jan.oravec at 6com.sk               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
 Cc: 
-Summary: xsp-1.1.18 on mono-1.2 throws random exceptions when serving web services requests
+Summary: [amd64-only] xsp-1.1.18 on mono-1.2 throws random exceptions when serving web services requests
 
 80% of cases when I try to access web service method hosted on XSP 1.1.18
 on Mono 1.2 on amd64 architecture I get this exception:
 
 
 System.Exception: Error reading headers.
@@ -128,6 +128,18 @@
         /usr/bin/mono [0x5106a2]
         /usr/bin/mono [0x4dc9ad]
         /lib/libpthread.so.0 [0x2b902dc5dd00]
         /usr/bin/mono [0x49b366]
         [0x410fb326]
 Aborted
+
+------- Additional Comments From jan.oravec at 6com.sk  2006-11-21 19:22 -------
+I have been able to test our application on x86 where it appears to
+work correctly (same versions of Mono and XSP). Furthermore, I tested
+a lot of random WebService code using MySQL.Data.dll (both 1.0.7 and
+1.0.8) hosted under XSP on amd64. Almost every code resulted in random
+exceptions, segfaults, other errors (e.g. DNS resolver not able
+(exception) to resolve hostname of mysql server, when tcpdump on port
+53 clearly shown that it resolved) so I believe it is related to amd64
+code. When same code is runned directly and not through XSP, it works.
+I suspect it to be memory corruption with more application domains
+(which XSP creates AFAIK).