Okhttp: OkHttpClient ReadTimeout affected by response.body() ?

[axierjhtjz]

After setting some timeout values my GET request still surpasses 32 seconds. I noticed that the main bottleneck is on response.body() method which I don't know if has something to do with the ReadTimeout value.

Could it be that the json that I´m retrieving its just big and substracting it from the Response object it´s slow?

APIClient  D  getConnectTimeout: 10000
                 D  getWriteTimeout: 10000
                 D  getReadTimeout: 20000

Thanks.

[swankjesse]

The read timeout will only trigger if no data is returned for the full timeout. If the response is being streamed steadily but slowly, the timeout won't trigger. You might be able to get that with Okio's deadline.

You can get the timeout from response.body().source().
http://square.github.io/okio/okio/Timeout.html

[axierjhtjz]

Thanks @swankjesse. It worked like a charm.

Response response = client.newCall(request).execute();
BufferedSource bufferedSource = response.body().source();
Timeout timeout = bufferedSource.timeout();
timeout.deadline(20, TimeUnit.SECONDS);
String str = response.body().string();

Throwed the following.

System.err  W  java.io.InterruptedIOException: timeout

I´m adding the code here just in case someone needs it.