https://bz.apache.org/bugzilla/show_bug.cgi?id=57921
--- Comment #10 from Andrey Pokhilko <[email protected]> --- I've spenc several hours investigating the whole topic of closed keep-alive sockets with HTTPClient and I found: 0. There is no way to tell if server has closed socket in Java without reading from socket 1. HTTPClient throws NoHTTPResponse exception when it failed to read anything from server, most of the times this means server has closed the socket 2. It is suggested by HTTPClient authors to do one retry in case of NoHTTPResponse to make sure the problem persists 3. Since HTTPClient 4.3 there is special "RetryExec" class to cover this set of cases (JMeter using version 4.2) I see no efficient steps here until we will upgrade HTTPClient. Maybe just catching and retrying once on NoHTTPResponse might mitigate the case and separate it from other exception cases. -- You are receiving this mail because: You are the assignee for the bug.
