thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jake Farrell <jfarr...@apache.org>
Subject Re: ruby thrift client times out even though server responds immediately
Date Wed, 14 Mar 2012 13:42:07 GMT
Can you send your sample client and server that are showing these issues please

-Jake





On Mar 13, 2012, at 8:42 PM, T Vinod Gupta wrote:

> you mean what transport i am using? im using binary protocol though. the
> data as such is some strings and numbers.
> i dont know about writing bytes part.. at the api layer, we are just
> returning the return struct. no accounting of bytes over there.
> 
> thanks
> 
> On Tue, Mar 13, 2012 at 2:07 PM, Jean-Baptiste Quenot <jbq@caraldi.com>wrote:
> 
>> 2012/3/11 T Vinod Gupta <tvinod@readypulse.com>
>> 
>>> has anyone seen this problem before? in my case, the ruby client throws a
>>> socket timeout exception, even though the server logs show that the
>>> response was sent back immediately. the timeout is set to be high (like
>> 10
>>> sec) and the response is server in less than a second.
>>> 
>>> #<Thrift::TransportException: Socket: Timed out
>>> reading 4096 bytes from <hostname>:9090>
>>> Socket: Timed out reading 4096 bytes from <hostname>:9090
>> 
>> 
>> What type of message are you returning?  Are you effectively writing 4096
>> bytes to the output?
>> --
>> Jean-Baptiste Quenot
>> 


Mime
View raw message