https://bz.apache.org/bugzilla/show_bug.cgi?id=63110
Philippe Mouawad <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |[email protected] | |om --- Comment #2 from Philippe Mouawad <[email protected]> --- Hello, The keepalive feature is part of our integration tests, so I don't think it is broken. Still, to check, can you modify log4j2.xml: <Logger name="org.apache.http" level="debug" /> <Logger name="org.apache.http.wire" level="error" /> And then run a test with 1 thread. Comparing Java and HC4 is meaningless, Java implementation is not realistic in terms of Connection management and we have very low control on reuse. Have you checked that your injector is not reaching ephemeral port limits and that you need to adjust it ? https://serverfault.com/questions/261663/on-linux-how-can-i-tell-how-many-ephemeral-ports-are-left-available As you have spot it, in version 5.0, there is a change in the way we handle ssl handshake on thread group iteration, previously (4.0) we would reuse ssl state, we don't anymore which can also increase load on your server: What results do you get with a test where: httpclient.reset_state_on_thread_group_iteration=false Thanks -- You are receiving this mail because: You are the assignee for the bug.
