[Mono-bugs] [Bug 670804] New: Asynchronous socket callbacks do not work in Mono/Linux

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=670804

https://bugzilla.novell.com/show_bug.cgi?id=670804#c0


           Summary: Asynchronous socket callbacks do not work in
                    Mono/Linux
    Classification: Mono
           Product: Mono: Runtime
           Version: 2.8.x
          Platform: Other
        OS/Version: Ubuntu
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: misc
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: alex_syd1 at yahoo.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: Other
           Blocker: Yes


Created an attachment (id=413159)
 --> (http://bugzilla.novell.com/attachment.cgi?id=413159)
server and client applications to demonstrate the bug

Description of Problem:
Client-server communication via asynchronous TCP sockets does not work in
Linux. Client only receives the very first message from the server. Calling
BeginReceive() for the subsequent messages causes the client to hang.

Steps to reproduce the problem:
1. Build the server solution from the attachment using MS Visual Studio 2008.
2. Build the clientasynclocal solution from the attachment using MS Visual
Studio 2008.
3. Launch server.exe in Windows.
4. Launch clientasynclocal on the same PC.
In a few seconds both apps will terminate. Note down their console listings.
5. Install Mono 2.8.2 in Linux.
6. Launch the same binary of server.exe on Linux in a shell (or alternatively
build the binary from the sources with Mono/xbuild).
7. Launch the same binary of clientasynclocal.exe on Linux in a shell (or
alternatively build the binary from the sources with Mono/xbuild).
In a few seconds both apps will enter wait state. Note down their console
listings.

Actual Results:
See comments in the Program.cs files in both the server and the
clientasynclocal solution.

Expected Results:
See comments in the Program.cs files in both the server and the
clientasynclocal solution.

How often does this happen? 
Always

Additional Information:
Software used:
- Windows 7 Professional
- MS Visual Studio 2008 with .NET 3.5 SP1
- Linux: Ubuntu 10.10
- Mono 2.8.2
The bug does NOT happen if using synchronous communication instead of
asynchronous.

I'm aware that I should not mindlessly tag a bug as critical only because it is
important to me. However if this particular bug is genuine, I believe it is a
showstopper, as it precludes using fundamental TCP socket functionality.

-- 
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.