Home/ Questions/Q 9198221
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-17T22:14:12+00:00

I have an win7 application where i am sending data b\w 2 clients on

  • 0

I have an win7 application where i am sending data b\w 2 clients on a TCP connection. While testing i found out that i was getting WSAEWOULDBLOCK error frequently on my socket. To
resolve this error i put a while loop around it for ex.

do  
{  
size_t value = ::send();  /*with proper arguments*/
}while(GetLastError() == 10035);

So if i get error 10035 i will resend the data.

But now i see that this while loop runs sometimes infinitely and my application goes
into kind of deadlock state. I tried increasing the size of socket but still of no use.

If anybody has any idea how to resolve WSAEWOULDBLOCK error please let me know.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    WSAEWOULDBLOCK is not really an error but simply tells you that your send buffers are full. This can happen if you saturate the network or if the other side simply doesn’t acknowledge the received data. Take a look at the select() function, which allows you to wait until buffer space is available or a timeout occurs. There is also a way to bind a win32 event to a stream, which then allows its use with WaitForMultipleObjects in case you want to abort waiting early.

    BTW: I initially wanted to object against your use of the term “deadlock”, but this is also something that could be happening: If you wait to send some some response before receiving the next request, and the other side wants to send a next request instead of receiving your response, your applications are effectively deadlocked. Using select(), you can determine whether you can send data, receive data or that the connection has failed, which allows you to handle these case correctly and when they occur.

    Note: I also assume that your code is not really a call to socket() but one to send/recv.

    • 0