Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
-
None
-
Unknown
Description
Class AsynchHTTPConduit method setupConnection(). Codeblock:
RequestConfig.Builder b = RequestConfig.custom() .setConnectTimeout((int) csPolicy.getConnectionTimeout()) .setSocketTimeout((int) csPolicy.getReceiveTimeout()) .setConnectionRequestTimeout((int) csPolicy.getReceiveTimeout());
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.
Attachments
Issue Links
- relates to
-
CXF-7122 Infinite loop due to AsyncHTTPConduit read timeout with exhausted connection pool
- Closed