hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Asankha C. Perera" <asan...@apache.org>
Subject Separating Connection Timeouts from Socket Timeouts
Date Wed, 27 Aug 2014 16:39:55 GMT
Hi All

The HttpAsyncRequestExecutor.timeout() method triggers a failed(new 
SocketTimeoutException()) on the FutureCallback while the 
RouteSpecificPool.timeout() also triggers the same.

Hence from within the FutureCallback we cannot distinguish if the cause 
is a Connection timeout or a Socket timeout. Should we change the 
RouteSpecificPool.timeout() to trigger a failed(new 
java.net.ConnectException()) instead?


Asankha C. Perera
AdroitLogic, http://adroitlogic.org


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

View raw message