hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HTTPASYNC-4) DefaultHttpAsyncClient does not execute callbacks on timeout
Date Thu, 07 Jul 2011 22:26:16 GMT

     [ https://issues.apache.org/jira/browse/HTTPASYNC-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Oleg Kalnichevski updated HTTPASYNC-4:
--------------------------------------

    Fix Version/s: 4.0-alpha3

> DefaultHttpAsyncClient does not execute callbacks on timeout
> ------------------------------------------------------------
>
>                 Key: HTTPASYNC-4
>                 URL: https://issues.apache.org/jira/browse/HTTPASYNC-4
>             Project: HttpComponents HttpAsyncClient
>          Issue Type: Improvement
>    Affects Versions: 4.0-alpha2
>         Environment: Max OS X 10.6.7, Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02-334,
mixed mode)
>            Reporter: A. Diamond
>             Fix For: 4.0-alpha3
>
>
> When I pass a FutureCallback to be executed with an HttpRequest, I can specify handlers
for completed, cancelled and failed.
> Unfortunately, if the request fails because the server does not respond in time, the
"failed" handler of the FutureCallback never gets notified. It looks like the timeout method
in org.apache.http.impl.nio.client.NHttpClientProtocolHandler simply closes the connection
and returns.
> We would like to be able to handle requests that timed out-- either logging them or queuing
them for later retries.
> Is it possible to fire the "failed" callback with an exception indicating timeout?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Mime
View raw message