[reSIProcate] Intermittent problems using TCP on windows

[Scott Godin]

I found a reference that indicates we should be treating EAGAIN and
EWOULDBLOCK (WSAEWOULDBLOCK) the same.  I will change the resip code for
this.

http://stackoverflow.com/questions/7003234/which-systems-define-eagain-and-ewouldblock-as-different-values

Thanks!

Scott

On Thu, Jun 20, 2013 at 5:29 AM, Jan Granqvist <jan_granqvist at yahoo.com>wrote:

> Hi all,
>
> I have ran into some intermittent problems using TCP on windows.
>
> The output trace shows
> INFO | 20130618-100055.445 | SIPCService | RESIP:TRANSPORT | 7948 |
> TcpConnection.cxx:97 | Failed write on 3532 Unknown error
> from method TcpConnection::write.
>
> I added to the trace the actual error code returned from windows, which
> states 10035(WSAEWOULDBLOCK).
> However, the caller(Connection::performWrite) there's a check against
> error code EAGAIN.
>
> Could there be some mismatch here when running on windows?
>
> Thanks
> /Janne
>
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at resiprocate.org
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20130620/4f090d57/attachment.htm>