cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Freeman Fang (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CXF-6910) don't need setSocketTimeout when create ahc RequestConfig
Date Fri, 20 May 2016 01:57:12 GMT
Freeman Fang created CXF-6910:
---------------------------------

             Summary: don't need setSocketTimeout when create ahc RequestConfig
                 Key: CXF-6910
                 URL: https://issues.apache.org/jira/browse/CXF-6910
             Project: CXF
          Issue Type: Improvement
          Components: Transports
            Reporter: Freeman Fang


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
{code}
protected synchronized HttpResponse getHttpResponse()
{code}
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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message