[Mono-bugs] [Bug 610659] New: Wcf NetTcpBinding only allows one client at a time

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Tue Jun 1 11:38:31 EDT 2010



           Summary: Wcf NetTcpBinding only allows one client at a time
    Classification: Mono
           Product: Mono: Class Libraries
           Version: 2.6.x
          Platform: x86-64
        OS/Version: Linux
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: WCF
        AssignedTo: atsushi at ximian.com
        ReportedBy: alex.cepoi at gmail.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---

Created an attachment (id=366151)
 --> (http://bugzilla.novell.com/attachment.cgi?id=366151)
just a basic client-server wcf application

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/533.4
(KHTML, like Gecko) Chrome/5.0.375.53 Safari/533.4

In a client-server Wcf application using NetTcpBinding first client connects
with no issues. All other clients connections hang until first client
disconnects and so on...

So only one client can ever be connected to a server, which is, of course, no

Tested multiple times on multiple examples (Duplex or Simplex). Tested on
2.6.3, 2.6.4 and the latest svn revision as of today (158277).

Works without issue in .NET.

Reproducible: Always

Steps to Reproduce:
1. Build a client-server Wcf application (NetTcpBinding)
2. Start Server
3. Connect with at least two clients
Actual Results:  
Only the first client connects and others hang.

Expected Results:  
All clients connect to server

Although any wcf application will do, i have uploaded one of my basic examples
(monodevelop project).

I understand that NetTcpBinding is far from complete, but i feel it is missing
event the most basic of functionality. Please inform me if/when to expect
progress with this bug.

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

More information about the mono-bugs mailing list