[
https://issues.apache.org/jira/browse/CXF-7623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16342581#comment-16342581
]
Dennis Kieselhorst commented on CXF-7623:
-----------------------------------------
This has been merged as part of a PR https://github.com/apache/cxf/pull/190 as
fix for CXF-7122. [~willymontaz] [~ffang] can you please take a look?
> AsynchHTTPConduit setupConnection - timeout settings
> ----------------------------------------------------
>
> Key: CXF-7623
> URL: https://issues.apache.org/jira/browse/CXF-7623
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Reporter: Antonin Fischer
> Priority: Minor
> Fix For: 3.2.2
>
>
> Class AsynchHTTPConduit method setupConnection(). Codeblock:
> {code:java}
> RequestConfig.Builder b = RequestConfig.custom()
> .setConnectTimeout((int) csPolicy.getConnectionTimeout())
> .setSocketTimeout((int) csPolicy.getReceiveTimeout())
> .setConnectionRequestTimeout((int)
> csPolicy.getReceiveTimeout());
> {code}
> Line *setConnectionRequestTimeout((int) csPolicy.getReceiveTimeout())*
> Settings of request timeout with receive timeout is not backward compatible
> solution. In addition the receive timeout is in many times to long. Better
> way is set the *request timeout by connection timeout* instead of it. It is
> still compromis solution.
> HTTPClientPolicy object still doesn't contain request timeout. Think about
> extension of domain objects about request timeout which is already used in
> pools etc.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
