Project

General

Profile

Task #3057

Story #2246: refactor libclient_java connection management

retest CLOSE_WAIT issue once the lib client is complete.

Added by Rob Nahf over 9 years ago. Updated almost 7 years ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
d1_libclient_java
Target version:
Start date:
2012-07-09
Due date:
% Done:

30%

Story Points:
Sprint:


Related issues

Related to Infrastructure - Story #3058: upgrade HTTPComponents from 4.1.3 to 4.2.1 Closed 2012-07-09 2014-12-15
Related to Infrastructure - Bug #5311: MultipartRequestResolver leaking resources (open file handles) Closed 2014-05-02 2014-05-10

History

#1 Updated by Rob Nahf over 7 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 7 years ago

  • Milestone changed from None to CCI-1.4
  • Product Version set to 1.4.0

#3 Updated by Robert Waltz about 7 years ago

  • Target version set to Release Backlog

#4 Updated by Robert Waltz about 7 years ago

  • Product Version changed from 1.4.0 to *

#5 Updated by Rob Nahf about 7 years ago

  • Target version changed from Release Backlog to CCI-2.0.0

#6 Updated by Rob Nahf almost 7 years ago

  • % Done changed from 80 to 90

closeIdleConnections should have been removed from v2.0. check to make sure.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)