[Mono-bugs] [Bug 633870] New: Socket.SendTimeout does not throw an exception when timeout expires

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Mon Aug 23 18:56:00 EDT 2010



           Summary: Socket.SendTimeout does not throw an exception when
                    timeout expires
    Classification: Mono
           Product: Mono: Class Libraries
           Version: 2.6.x
          Platform: x86-64
        OS/Version: Ubuntu
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: CORLIB
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: greg.smolyn at strangeloopnetworks.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_4; en-US)
AppleWebKit/534.6 (KHTML, like Gecko) Chrome/6.0.495.0 Safari/534.6

If you set the SendTimeout value on a socket object, the socket.Send() method
should throw a SocketException if the timeout expires while it is still

This is especially important in Blocking mode, where Send() will block until

Reproducible: Always

Steps to Reproduce:
1. Set up a client/server
2. Create a socket and set the SendTimeout to something small (500)
3. Send something really really large to the server that will take longer than
500ms (you can set up the server to stop reading after some small amount)
Actual Results:  
Send method will exit with a return value showing the number of actual bytes
sent. This will be less than the total bytes needed to be sent.  No exception
will be thrown.

Expected Results:  
A SocketException should be thrown indicating the timeout expired.

A project file should be on it's way soon.

Configure bugmail: https://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.

More information about the mono-bugs mailing list