Re: !EventConnect Problem
- From: "Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT com>
- Date: Tue, 19 Jun 2007 07:50:00 -0700
The message is printed, best I can read, in the following situations:
1. The socket is not in a listening state. Presumably, this would occur if
you bound a socket to the right TCP port number, but didn't call listen.
2. The address family of the incoming connection doesn't match that of the
socket bound to the port (and listening).
3. There's a problem with the connection address, sockaddr. I'd have to
read a bunch more code to see what exactly this is testing for.
4. The incoming connection queue has no room for connections. I suppose
this might happen if you called listen( 0 ), or if you already had enough
pending connections to the listening socket that there wasn't room for
another potential client.
Paul T.
"Doug Allender" <doug.allender@xxxxxxxxx> wrote in message
news:2A9573EE-7565-433A-B7F9-43BEDBBF44A7@xxxxxxxxxxxxxxxx
We have a C++ application which uses a lot of TCP connections, and has a
bug
we are currently trying to trace. We are using WinCE 4.2 on an arm
platform,
and recieve the following message, repeatedly when our problem occurs
"!EventConnect: connect not accepted IncConnQ = 0". Has anyone else seen
this
message, or can anyone point me in the correct direction.
--
Snr. Des. Eng.
Northern Hi-Tec
.
- Follow-Ups:
- Re: !EventConnect Problem
- From: Doug Allender
- Re: !EventConnect Problem
- Prev by Date: Re: .netCF paint speed
- Next by Date: AlphaBlend API
- Previous by thread: Re: .netCF paint speed
- Next by thread: Re: !EventConnect Problem
- Index(es):
Relevant Pages
|
Loading