users@jersey.java.net

Re: [Jersey] client connection timeout read timeout settings

From: Paul Sandoz <Paul.Sandoz_at_Sun.COM>
Date: Thu, 16 Jul 2009 19:21:55 +0200

Hi,

By default they follow the same semantics as that for HttpURLConnecton:

   http://java.sun.com/j2se/1.5.0/docs/api/java/net/URLConnection.html#setConnectTimeout(int)

   http://java.sun.com/j2se/1.5.0/docs/api/java/net/URLConnection.html#setReadTimeout(int)

So the read time out starts when the first byte is attempted to be
read from the input stream of the response, after the connection has
been established.

Paul.

On Jul 16, 2009, at 7:13 PM, Saavedra, Gisella wrote:

> Just need a clarification. Maybe these are standard tcp concepts,
> but I could not find a precise definition.
>
> · Do these counters intercept?
> · Or the connection timeout starts and ends (ends when the
> client can connect to the web service) before the read timeout, ??
> · Does the read timeout starts kicking when the connection
> is established (so does it include the time that it takes the web
> service to execute?), or
> does it start kicking when the response is sent to
> the client until all the data sent has been received by the client.
>
> Thanks.
>
> Gisella Saavedra
> Sr. Software Engineer
> gsaavedra_at_zebra.com
> <image001.gif>
> 1000 Broadway, Suite 150, Oakland, CA 94607 | T+1 510 267 5123 T
> Main+1 510 267 5000 F+1 510 267 5100 | http://www.zebra.com/zes
>
>
>