Re: Winsocks: 10038/WSAENOTSOCK after accept()
- From: "Arkady Frenkel" <arkadyf@xxxxxxxxxxxxxxxx>
- Date: Thu, 13 Sep 2007 06:59:12 +0300
Check maybe that problem connected to backlog, only 5 allowered in client Os
(XP/Vista ) opposite to 200 in Server's Os
Arkady
"Moritz Armingeon" <armingeon@xxxxxxxxx> wrote in message
news:97f40$46e6fdf1$4d38fd17$15743@xxxxxxxxxxxxxxxxxx
Hello!
I'm running a webserver for a webservice. It's written in unmanaged C++.
On high a frequency of connections, maybe 20 per second, it becomes
unstable.
accept() on a new client socket returns INVALID_SOCKET and
WSAGetLastError() returns 10038.
With lower frequencies, the webserver stays stable though. What could be
the cause of such an bevavior? Maybe local socket limitations? Netstat
lists many sockets in state TIMED_WAIT.
Regards, Moritz
.
- Follow-Ups:
- Re: Winsocks: 10038/WSAENOTSOCK after accept()
- From: Alexander Nickolov
- Re: Winsocks: 10038/WSAENOTSOCK after accept()
- References:
- Winsocks: 10038/WSAENOTSOCK after accept()
- From: Moritz Armingeon
- Winsocks: 10038/WSAENOTSOCK after accept()
- Prev by Date: Re: Protocols pros and cons
- Next by Date: Re: searching another computer
- Previous by thread: Re: Winsocks: 10038/WSAENOTSOCK after accept()
- Next by thread: Re: Winsocks: 10038/WSAENOTSOCK after accept()
- Index(es):
Relevant Pages
|
|