You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Ben Craig (JIRA)" <ji...@apache.org> on 2013/08/28 23:55:52 UTC
[jira] [Updated] (THRIFT-1892) Socket timeouts are declared in
milli-seconds, but are actually set in micro-seconds
[ https://issues.apache.org/jira/browse/THRIFT-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ben Craig updated THRIFT-1892:
------------------------------
Attachment: winsock_mstimeouts.patch
haven't tried applying this on a clean checkout, but it gets the idea across. Either this, or something very similar to it will be my approach.
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira