You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Györgyey Tamás (JIRA)" <ji...@apache.org> on 2018/10/24 15:45:00 UTC
[jira] [Created] (CXF-7883) Handle connectionRequestTimeout in
AsyncHTTPConduitFactory
Györgyey Tamás created CXF-7883:
-----------------------------------
Summary: Handle connectionRequestTimeout in AsyncHTTPConduitFactory
Key: CXF-7883
URL: https://issues.apache.org/jira/browse/CXF-7883
Project: CXF
Issue Type: Bug
Components: Transports
Affects Versions: 3.2.6
Reporter: Györgyey Tamás
If connections are contended towards a slow target, it may make sense
to set connectionTimeout and connectionRequestTimeout to values much lower than
the receiveTimeout. Expected client behavior is to receive an error if a connection
does not become available within connectionRequestTimeout. Current behavior however
is that the error is only received after up to receiveTimeout has passed, when a
current request to the target has finished and the connection is released or returned
to the pool.
This causes a possible build-up of pending requests in memory for the duration of receiveTimeout instead of connectionRequestTimeout.
See github PR: https://github.com/apache/cxf/pull/466
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)