I have seen weirdness like that when client was on a VM-Host and server was on a VM-guest (and thus should see no issues) the past where it seemed that there was some absurd delay in receiving responses. I do not have any of the captured data though.
I would say you should TCP-dump at the client side and add some visually noticeable data (like a string) so that it would be easy to trace in the tcpdump output. On Sun, Mar 11, 2012 at 3:52 PM, T Vinod Gupta <[email protected]>wrote: > hi, > 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 > > thanks >
