[jira] [Commented] (THRIFT-1892) Socket timeouts are declared in milli-seconds, but are actually set in micro-seconds

["Jens Geyer (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/THRIFT-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790818#comment-13790818 ] 

Jens Geyer commented on THRIFT-1892:
------------------------------------

I can't manage that one to apply successfully, sorry. Seems not to be EOL this time.

> Socket timeouts are declared in milli-seconds, but are actually set in micro-seconds
> ------------------------------------------------------------------------------------
>
>                 Key: THRIFT-1892
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1892
>             Project: Thrift
>          Issue Type: Bug
>          Components: C++ - Library
>    Affects Versions: 0.9
>         Environment: Windows 8 x64
>            Reporter: Alexander
>            Assignee: Ben Craig
>            Priority: Minor
>              Labels: cpp, socket, timeout
>         Attachments: winsock_mstimeouts.patch
>
>
> Socket timeouts are declared in milliseconds in TSocket.h:
>   /**
>    * Set the connect timeout
>    */
>   void setConnTimeout(int ms);
>   /**
>    * Set the receive timeout
>    */
>   void setRecvTimeout(int ms);
>   /**
>    * Set the send timeout
>    */
>   void setSendTimeout(int ms);
> But, when i set timeout which is supposed to be 5000 seconds, and make a call to the service function that intentionally hangs, ETIMEDOUT exception occurs precisely after 5 seconds.
>   socket->setConnTimeout(5*1000*1000);
>   socket->setRecvTimeout(5*1000*1000);
>   socket->setSendTimeout(5*1000*1000);



--
This message was sent by Atlassian JIRA
(v6.1#6144)