On Mon, 2012-06-11 at 13:20 -0400, Joshua Spiewak wrote: > On Mon, Jun 11, 2012 at 11:28 AM, Oleg Kalnichevski <[email protected]>wrote: > > > On Mon, 2012-06-11 at 10:12 -0400, Joshua Spiewak wrote: > > > What about the scenario where a service is behind a load balancer? > > > In this case, one of two instances of the service is slow, and the load > > > balancer takes it out of service. A second request is required in order > > to > > > succeed, as opposed to just waiting twice as long. > > > > > > I am not sure I understand your second paragraph. Are you saying that > > since > > > STE is a subclass of IOE, that you think an idempotent requests _should_ > > be > > > retried, or _should not_ be retried? > > > > > > > Excuse my being such a mess. Yes, I meant to say SocketExceptions were > > expected to be retried automatically provided other conditions (such as > > request idempotency) were satisfied. > > > > > No problem. But back to my original point, SocketTimeoutException extends > InterruptedIOException, and that is explicitly not retried. So is that a > bug? > >
No, this is intended. InterruptedIOException are not automatically re-tried per default. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
