Re: !EventConnect Problem

We can't seem to find any of the above causing us problems, but for what its
worth I'll give you some more info, which may or may not be usefull.

We have our CE unit being polled by a PC to provide data via tcp/ip. with a
poll time of 500mS we get a break in communication approx once a day, this is
approx 2 minuts and accompanied by

0x83a2d400: ndisMResetCompleteStage2: Internal reset
0x83a2d400: *InsertTCB: SetIdleTimerReset
0x83a2d400: InsertTCB: setting fTCBTimerOn to 0
0x83a2d400: *InsertTCB: Restarting TCBTimer
.... may get several copies of the TCB Timeouts.

with a poll every 5 seconds the 2 minute brakes were very infrequent
(approx every 8 days), but about once every 2 days we would get a break of
approx 20minutes when the event connect messasges are generated over and over.

we also see the event connect messages if we try to use the remote
performance tool... so? I'm not sure where I'm going from here. The socket
server we are using is multi-threaded, however this only seens to have about
4 threads running to deal with the communications we have going on.

any thoughts
--
Snr. Des. Eng.
Northern Hi-Tec


"Paul G. Tobey [eMVP]" wrote:

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



.

Relevant Pages

  • Re: accept 1000 or more incoming conection
    ... The listen function places a socket a state where it is listening for ... SOCKET s, ... Now i have developed a client that Makes 500 connection to a server at ...
    (comp.programming.threads)
  • Re: Socket and cycle problem
    ... listening this port countinously. ... So I need make some loop to print data from 3883 port permanent. ... the data it receives from each connection after the remote side drops ... If you were to use the socket module, then it would look something like this: ...
    (comp.lang.python)
  • Re: lock on accept
    ... | 'accept' and then makes a connection to itself. ... descriptor given to each for the one socket that is connected? ... Checking the apache lists and code comments ... | listen on more than one port, which means more than one listening ...
    (comp.unix.programmer)
  • Re: Listen() Winsock query...
    ... That mean that when acceptreturn socket handle that connection described ... If listen is called on an already listening socket, ...
    (microsoft.public.win32.programmer.networks)
  • Re: !EventConnect Problem
    ... The socket is not in a listening state. ... There's a problem with the connection address, ... The incoming connection queue has no room for connections. ...
    (microsoft.public.windowsce.app.development)