ksewen created HTTPCLIENT-2299:
----------------------------------
Summary: The socketTimeout parameter in ConnectionConfig does not
take effect when reusing an existing connection.
Key: HTTPCLIENT-2299
URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2299
Project: HttpComponents HttpClient
Issue Type: Bug
Components: HttpClient (classic)
Affects Versions: 5.3-alpha1
Reporter: ksewen
Attachments: invalid-socket-time-out.jpg
I have created an instance of PoolingHttpClientConnectionManager and set a
socket timeout of 5 seconds in the ConnectionConfig. In this case, when
accessing a backend service with a response time of 10 seconds for the first
time, a SocketTimeoutException was correctly thrown. But in the second request,
when reusing an already established connection, the client waited for 10
seconds and completed the request. Instead, if I set a 5-second SoTimeout in
SocketConfig and run the test again. The setting works.
runnable test cases: [https://github.com/ksewen/httpclient-demo]
I have uploaded an attachment that demonstrates the configured value of the
{{SocketTimeout}} when the connection is being reused.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
