geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <>
Subject [jira] Commented: (GERONIMO-3617) AsyncHttpClient should support retries on connection failures
Date Mon, 17 Dec 2007 23:01:46 GMT


Sangjin Lee commented on GERONIMO-3617:

The number of retries would probably be a parameter on the AsyncHttpClient instance itself,
as it pertains more to the client app than individual requests.  The default should be 0 (no

The natural place where this would be attempted I think is AsyncHttpClient.FutureListener.
 FutureListener is the listener on the connect future.  There one can deal with successful
connections as well as failures.

One could maintain the retry count on the FutureListener, and call connect() until the retry
count is exhausted.  The FutureListener object could (and probably should) be reused for subsequent
retry attempts to keep track of the count.

> AsyncHttpClient should support retries on connection failures
> -------------------------------------------------------------
>                 Key: GERONIMO-3617
>                 URL:
>             Project: Geronimo
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: AsyncHttpClient
>    Affects Versions: 1.x
>            Reporter: Sangjin Lee
> AsyncHttpClient should provide a way to support retries if initial connection attempts
fail.  There should be a configuration where connection retries are enabled and also the maximum
number of attempts is specified.  If these are set, connection attempts should be retried.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message