[Mono-bugs] [Bug 57845][Blo] Changed - WebRequest/WebResponse busted

[bugzilla-daemon@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 james@ximian.com.

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

--- shadow/57845	2004-05-05 13:11:56.000000000 -0400
+++ shadow/57845.tmp.24750	2004-05-05 13:30:17.000000000 -0400
@@ -1,16 +1,16 @@
 Bug#: 57845
-Product: Mono: Class Libraries
+Product: Mono: Runtime
 Version: unspecified
 OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
 Severity: Unknown
 Priority: Blocker
-Component: System
+Component: misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: james@ximian.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
 URL: 
 Cc: 
@@ -56,6 +56,32 @@
 doing looks at the bug :)
 
 ------- Additional Comments From james@ximian.com  2004-05-05 13:11 -------
 Also, I'm still getting the exception message/abort with some other
 code I have which uses WebRequest/WebResponse, but I'm not able to
 write a test case that exposes it....
+
+------- Additional Comments From james@ximian.com  2004-05-05 13:30 -------
+Ok, when running my app in mint, I get the following trace when
+calling request.GetResponseStream ()
+
+System.Net.WebException: Error getting response stream: ReceiveFailure
+---> System.IO.IOException: BeginReceive failure
+#0: 0x00058 throw      in System.Net.Sockets.NetworkStream:BeginRead
+(byte[],int,int,System.AsyncCallback,object) (0x8885ee8 [0x87da000]
+[0] [4096] [0x883fb18] [0x8861cd0] )
+#1: 0x0002a callvirt   in System.Net.WebConnection:InitRead (object)
+([0x8861cd0] )
+#2: 0x0006f vcall      in System.Net.WebConnection:InitConnection
+(object,bool) (0x8861cd0 [0x88894c0] [0] )
+#3: 0x00000            in System.Threading.WaitOrTimerCallback:Invoke
+(object,bool) (0x883faf0 [0x88894c0] [0] )
+#4: 0x00016 vcallvirt  in
+System.Threading.RegisteredWaitHandle:DoCallBack (object) (0x8843ab8
+[0x87dd030] )
+#5: 0x00000            in System.Threading.WaitCallback:Invoke
+(object) (0x883f9b0 [0x87dd030] )
+--- End of inner exception stack trace ---
+
+
+Also, if I run the test case I posted above in mint it doesn't
+segfault or do any nastiness like that.  So it appears to be a jitter bug.