TCP server stop receiving new connections
- From: Julián Rodríguez Bajo <julian.rodriguez@xxxxxxxxxx>
- Date: Mon, 09 Jul 2007 10:06:01 +0200
Hi folks.
I have a strange problem in my class library used by all our client and server applications.
There are servers listening on different ports for different purposes. Sometimes (when a lot of new clients try to connect to the same server), one of the servers (not allways the same one) stops accepting new incomming connections, but keeps current connections. Server port appears as LISTENING, but OnAccept never arrives to server. New client connections receive a WSAECONNREFUSED error. In this situation, if I call Accept directly in a test application, one incomming connection is accepted, but no messages can be sent cliet -> server nor server -> client, and after 15 seconds connection is dropped because of a custom keep alive mechanism. Running server and a lot of client applications in same machine fails the same way.
Both client and server processes use the same class library. The library is a statically linked MFC based static library. Both classes, server and client, derive from CAsyncSocket. There are no threads involved.
I have tried changing nConnectionBacklog parameter to Listen, but that does not seems to make any effect.
Any suggestion would be apreciated.
Best regards.
.
- Follow-Ups:
- Re: TCP server stop receiving new connections
- From: Ali
- Re: TCP server stop receiving new connections
- From: Arkady Frenkel
- Re: TCP server stop receiving new connections
- Prev by Date: Re: WlanSetProfile...how to create an adhoc connection
- Next by Date: Re: IP checksum
- Previous by thread: IP checksum
- Next by thread: Re: TCP server stop receiving new connections
- Index(es):
Relevant Pages
|