hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Asankha C. Perera" <asan...@apache.org>
Subject Re: Separating Connection Timeouts from Socket Timeouts
Date Wed, 27 Aug 2014 17:26:25 GMT
On 08/27/2014 10:43 PM, Oleg Kalnichevski wrote:
> On Wed, 2014-08-27 at 22:09 +0530, Asankha C. Perera wrote:
>> 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?
>>
>   +1
> Makes sense to me.
>
> Oleg
Thanks Oleg, I will update the code accordingly

regards
asankha

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

http://esbmagic.blogspot.com




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


Mime
View raw message