[
https://issues.apache.org/jira/browse/HTTPASYNC-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13772894#comment-13772894
]
dennis lucero commented on HTTPASYNC-55:
----------------------------------------
I also noticed this behaviour. The code is used in a HttpAsyncClient example
(http://hc.apache.org/httpcomponents-asyncclient-dev/httpasyncclient/examples/org/apache/http/examples/nio/client/AsyncClientHttpExchangeFutureCallback.java).
You mention a workaround, Oleg Kalnichevski, could you elaborate on how to use
IOReactor to set the connect and socket timeout?
Thanks
> Socket timeout set in RequestConfig does not work
> -------------------------------------------------
>
> Key: HTTPASYNC-55
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-55
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.0-beta4
> Reporter: Piotr Bartosiewicz
>
> Should this code work?
> final RequestConfig requestConfig = RequestConfig.custom()
> .setConnectTimeout(connectTimeout)
> .setSocketTimeout(socketTimeout)
> .build();
> final CloseableHttpAsyncClient httpClient = HttpAsyncClients.custom()
> .setDefaultRequestConfig(requestConfig)
> .build();
> At least socket timeout does not work.
> I fount a workaround to set this timeouts in IOReactor.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
