[Mono-bugs] [Bug 514591] New: HttpWebRequest.Abort on a non-responsive asynchronous HttpWebRequest, leaves the TCP socket open.

[bugzilla_noreply at novell.com]

http://bugzilla.novell.com/show_bug.cgi?id=514591


           Summary: HttpWebRequest.Abort on a non-responsive asynchronous
                    HttpWebRequest, leaves the TCP socket open.
    Classification: Mono
           Product: Mono: Class Libraries
           Version: 2.4.x
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: System
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: bassam at symform.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---


Created an attachment (id=299159)
 --> (http://bugzilla.novell.com/attachment.cgi?id=299159)
Repro

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.10)
Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729)

When calling Abort() on a non-responsive asynchronous HttpWebRequest in a
timeout-callback routine, the TCP socket on OS level remains open with a
state of SYN_SENT. 

This might be an issue that was brought up before. See
http://www.mail-archive.com/mono-bugs@lists.ximian.com/msg03735.html.

Attached is a repro.


Reproducible: Sometimes

Steps to Reproduce:
1. Compile the program attached.
2. Run it. 
Actual Results:  
dev:~$ mono MonoWebReqBug.exe
[2] Timeout
[4] Timeout
[1] Timeout
[5] Timeout
[3] Timeout
[6] ConnectFailure
[7] ConnectFailure
[0] Timeout
[8] Timeout
[9] Timeout
Done.

The process does not exit.

Netstat shows the following

Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      1 10.0.2.15:33140         78.23.55.11:65099       SYN_SENT



Expected Results:  
The process should exit.
Socket is closed.

Note that Abort() is the only mechanism for us to use to timeout async
requests.

-- 
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.