[Mono-bugs] [Bug 691423] New: Socket.Available == 1 when socket.Receive return 0

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Tue May 3 08:48:27 EDT 2011



           Summary: Socket.Available == 1 when socket.Receive return 0
    Classification: Mono
           Product: Mono: Class Libraries
           Version: 2.10.x
          Platform: i686
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: System
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: peter at endnode.se
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/534.16
(KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16

When a socket tcp connection is closed the socket.Receive return 0 bytes but
socket.Available still return 1.

Either socket.Available should return 0 since there is no more data to be read,
or socket.Receive misses the last byte.

This occurs in a http proxy but only a few times a day.

Reproducible: Sometimes

Steps to Reproduce:
1. Run HitProxy

2. When the process start to consume 100% cpu, the loop running gets stuck
since socket.Available == 1

I have received solution to my original problem elsewhere.
This bug is only about the socket.Available property.

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