WCF Duplex Service and TCP Port Exhaustion

Question

I'm trying to circle my head around this. I am creating a messaging application with a specific business, it is going to connect from 5000 to 10000 machines back to our data center via WCF (without vpns, all over the network). This is mainly for alerts, and I need to be able to send direclty messages to specific clients, and WCF allows me to do all this with a duplex contract, but with this many clients I had to think about maximizing TCP port space 65535.

I’m going to assume that all incoming connections will go through any port that I choose, but the garbage back to the clients will occupy one port each. I'm curious if WCF Port Exchange is working to solve this problem, or if there are only 65,535 ports per IP address? In this regard, how MSN Messenger and the like deal with this situation. Of course, I may never get to it, but at least I get into the area.

Or does the WCF duplex contract at the end of the service support opening a port for callback while the client is working or freeing it?

Answer 1

I think that each port is actually a combination of DestinationTCPAddress and Port Number - so you are not done.

.. , . .

Answer 2

- TCP , . , .

TIME-WAIT - , , - - 90 ( )

- , , , /

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

TcpTimedWaitDelay = 30
MaxUserPort = 65534 
MaxHashTableSize = 65536 
MaxFreeTcbs = 16000 

MSDN Technet . .

http://technet.microsoft.com/en-us/library/cc776295.aspx

- , . SQL, Biztalk, IIS ..

Answer 3

, , .

, , , . .

Answer 4

( , IP) , , . , , - .