A windows service with 30 odd sockets that's been running 24/7 for 18
months (barring monthly windows update reboots), died early this morning
with 10055 in TryToSend.  

Unfortunately, this logged error was itself being sent via a socket, so
repeated a few hundred times in less than a second, finally getting
'Error Send Data - Stack overflow' when the service stopped itself. 

All other TCP/IP activity on the PC died within a few minutes, but other
applications continued running normally.  

Unfortunately I did not check how many sockets/connections were open
before I rebooted the PC later in the morning, or memory status, but
unless the 400 megs of Windows updates last week has screwed TCP, I've no
reason anything on my PC is leaving lots of sockets open. 

Is there a way to check how much socket buffer space is left? 

If error 10055 occurs, should I immediately reboot the PC so the service
can restart?

To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Reply via email to