Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
NT
apps
dfs
dns
domain
dsmnfpnw
embedded
fsft
mail
misc
oemdsp.preinstall
personalfax
print
protocol.ipx
protocol.misc
protocol.ras
protocol.routing
protocol.tcpip
registry
setup
terminalserv.app.
terminalserv.client
terminalserv.connectivity
terminalserv.domain
terminalserv.misc
terminalserv.prot.rdp
terminalserv.prot.tcpip
terminalserv.setup
terminalserv.user
windowsnt.wntsee
  
 
date: Fri, 16 May 2008 15:46:46 -0500,    group: microsoft.public.windowsnt.protocol.tcpip        back       


WOULD BLOCK issue   
I've took over a C++ code that is connecting to a server via TCP.   The 
connect() call receives a WOULD BLOCK error.    Now it wasn't doing this, 
but as we started ramping up the connections to the server it went into this 
state.   Now we have rebooted both the client and server and we still get 
that error even with 1 connection.   I'm starting to wonder if we have blown 
the TCP stack.   Only issue I have with that statement is data seems to 
still be getting through.   We ran this from another client and it works 
fine, just the one client we maxed out does it have this issue.   Anyone 
understand why?
date: Fri, 16 May 2008 15:46:46 -0500   author:   Chizl

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us