I'm using release 4.2.1's AutoRetryHttpClient and trying to track down why my issued connections keeps going up when I have a retry strategy in place, and the server responds with a 503.
>From looking at the method: execute(HttpHost target, HttpRequest request, HttpContext context) it appears to me that in the for loop that implements the retry behaviour, the HttpResponse is not consumed if a retry should be attempted. On subsequent iterations, the backend creates new HttpResponse objects, leading to connections that are never closed. Am I reading this correctly? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
