Bug #7462: integration tests are getting frequent read timeouts
configure the HttpClient to allow more parallel connections
The PoolingConnectionManager defaults to 2 connections per route (server) and 20 total, and this is considered too restrictive by today's standards. (2 per server was in the rfc2616 spec, but was later dropped). Up the default to be congruent with current browsers.
#1 Updated by Rob Nahf over 6 years ago
modified HttpUtils, which creates the HttpClients for libclient. Not sure if we need to allow even further customization. An explanation on the optimal number has to do with network congestion if more connections are allowed per server. That's to say, it is unlikely that the number of connection per server will increase over time.