[HTTPCLIENT-2299] The socketTimeout parameter in ConnectionConfig does not take effect when reusing an existing connection.

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.3-alpha1
• Fix Version/s: 5.2.2, 5.3
• Component/s: HttpClient (classic)
• Assignee: Unassigned
• Reporter: ksewen
• Created: 20/Sep/23 06:25
• Updated: 23/Sep/23 09:05
• Resolved: 23/Sep/23 09:05

Description

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.