[Mono-bugs] [Bug 75025][Wis] Changed - When calling Abort() on a
non-responsive asynchronous HttpWebRequest,
the TCP socket remains open.
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Mon May 23 15:57:42 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 gonzalo at ximian.com.
http://bugzilla.ximian.com/show_bug.cgi?id=75025
--- shadow/75025 2005-05-23 02:57:51.000000000 -0400
+++ shadow/75025.tmp.2263 2005-05-23 15:57:42.000000000 -0400
@@ -1,12 +1,12 @@
Bug#: 75025
Product: Mono: Runtime
Version: 1.1
OS: unknown
OS Details:
-Status: NEW
+Status: ASSIGNED
Resolution:
Severity: Unknown
Priority: Wishlist
Component: misc
AssignedTo: gonzalo at ximian.com
ReportedBy: simon.brys at novell.com
@@ -43,6 +43,27 @@
- On Windows XP the Abort() call closes the socket correctly.
------- Additional Comments From simon.brys at novell.com 2005-05-22 09:45 -------
Created an attachment (id=15189)
Sample code to illustrate this issue. When running this program with a url of e.g. http://1.2.3.4, an exception will be thrown 180 seconds after the first Abort() call.
+
+------- Additional Comments From gonzalo at ximian.com 2005-05-23 15:57 -------
+I pointed your test at a windows XP computer running IIS. After a few
+successful requests, i enabled that firewall thing to stop incoming
+connections and got this:
+---------
+>>> Calling BeginGetResponse...done!
+>>> Timeout exceeded -- aborting webrequest
+*** RespCallback(): WebException raised! ***
+ Source: System
+ Message: Aborted.
+ Status: RequestCanceled
+---------
+
+Then disabled the firewall and the test started working again.
+
+So far, so good. Then I played enabling/disabling the firewall and at
+some point, all the requests were aborted, even when the server was
+expecting connections.
+
+I'll look into this now.
More information about the mono-bugs
mailing list