Story #2246: refactor libclient_java connection management
retest CLOSE_WAIT issue once the lib client is complete.
This implies that the default connection manager implement the connection-monitoring strategy that closes idle connections older than a couple minutes.
issue #2211 describes the problem.
#1 Updated by Rob Nahf almost 8 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 80
closeIdleConnections exhibits different behavior between v4.1 and 4.2. With inverting the dependency on HttpClient, managing connections can be removed from libclient, and left to applications that need to do so, (since they have a reference to the HttpClient.