[CXF-6910] don't need setSocketTimeout when create ahc RequestConfig

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.10, 3.1.7, 3.2.0
• Component/s: Transports
• Estimated Complexity: Unknown
• Assignee: Freeman Yue Fang
• Reporter: Freeman Yue Fang
• Created: 20/May/16 01:56
• Updated: 28/Oct/16 15:11
• Resolved: 20/May/16 02:01

Description

currently when we create the ahc RequestConfig we set the socketTimeout as
setSocketTimeout((int) csPolicy.getReceiveTimeout()

this cause the created http connection controlled by the socket level timeout, that said, if there's no data on the socket in a certain time, the connection would be closed, this overrule the TTL value of a connection, which means the connection timeToLive can't be managed by a connectionPoolManager, this is really painful for heavy loaded client request as we want the connectionPoolManager to manage the connection so that we could reuse the connection.

Fortunately in AsyncHTTPConduit

protected synchronized HttpResponse getHttpResponse()

we already handle the timeout at application level so that we needn't set that at socket level, so that let the connectionPoolManager can decide the connection TTL