Task #3057
Story #2246: refactor libclient_java connection management
retest CLOSE_WAIT issue once the lib client is complete.
30%
Description
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.
also
https://issues.apache.org/jira/browse/SOLR-861
https://forums.aws.amazon.com/thread.jspa?threadID=67603
http://stackoverflow.com/questions/4728683/workaround-to-not-shutdown-defaulthttpclient-each-time-after-usage
Related issues
History
#1 Updated by Rob Nahf over 10 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.
#2 Updated by Robert Waltz over 10 years ago
- Milestone changed from None to CCI-1.4
- Product Version set to 1.4.0
#3 Updated by Robert Waltz about 10 years ago
- Target version set to Release Backlog
#4 Updated by Robert Waltz about 10 years ago
- Product Version changed from 1.4.0 to *
#5 Updated by Rob Nahf about 10 years ago
- Target version changed from Release Backlog to CCI-2.0.0
#6 Updated by Rob Nahf almost 10 years ago
- % Done changed from 80 to 90
closeIdleConnections should have been removed from v2.0. check to make sure.
