Uploaded image for project: 'HttpComponents HttpClient'
  1. HttpComponents HttpClient
  2. HTTPCLIENT-2329

BasicHttpClientConnectionManager reuses closed connection objects

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Duplicate
    • 5.3.1
    • 5.4-beta1
    • None
    • None

    Description

      In the discardEndpoint method of InternalExecRuntime.java, the endpoint and connection are closed. The manager releases the connection with a timevalue of 0 ms. Because 0 is not considered positive, this leads to the expiration being set to Long.MAX_VALUE. Upon the next connection request, the manager will continue to use this unexpired connection object, even though it is closed. 
       
      The intention of the 0 ms timevalue was to have the connection expire immediately and then be discarded so that the manager will create a new connection for the next request.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            ttang Teresa Tang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment