[
https://issues.apache.org/jira/browse/HTTPASYNC-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski reassigned HTTPASYNC-105:
-------------------------------------------
Assignee: Oleg Kalnichevski
> socketTimeout is not reset back to default after a request that has specific
> timeout
> ------------------------------------------------------------------------------------
>
> Key: HTTPASYNC-105
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-105
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.1.1
> Reporter: Heikki Vesalainen
> Assignee: Oleg Kalnichevski
>
> Steps to reproduce:
> - Configure a custom HttpAsyncClient with IOReactorConfig that specifies a
> socketTimeout (SOTimeout) of 300000ms (5 mins). Have keep-alive be enabled
> (is by default)
> - Using the HttpAsyncClient, make a successfull GET request that specifies in
> the RequestConfig a socket timeout of 3000 ms (3 seconds)
> - Make a new request that on the server blocks for 60000ms using the same
> HttpAsyncClient, but do not specify any timeouts in RequestConfig.
> Expected: the second request should use the same connection and the request
> should succeed as the server blocks for 60000ms and the default timeout is
> 300000ms
> Actual: the second request is timed out after 3000ms because the
> socketTimeout of the connection is never resetted to the default after the
> request that altered it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
