Clarifying HttpURLConnection.disconnect() Behavior Regarding Resource Management and Connection Pooling

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: P4
    • None
    • Affects Version/s: 11, 17, 21, 25
    • Component/s: core-libs

      A DESCRIPTION OF THE PROBLEM :
      The documentation for HttpURLConnection.disconnect() is not clear as to when it should be called or what the effects are.
      For example, does disconnect need to be called in face of IOException from getInputStream or getErrorInputStream?
      If it is not called, does that lead to abandoned open sockets?
      Does calling it affect the http keep alive connection pool?

      FREQUENCY :
      ALWAYS

            Assignee:
            Unassigned
            Reporter:
            Webbug Group
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: