JDK-8216974 : HttpConnection not returned to the pool after 204 response
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.net
  • Affected Version: 13
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2019-01-14
  • Updated: 2020-06-23
  • Resolved: 2019-01-15
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 11 JDK 13
11.0.9-oracleFixed 13 b04Fixed
Related Reports
Duplicate :  
JDK-8241810 - Connections leaking with state CLOSE_WAIT with java.net.HttpClient
Relates :  
JDK-8211437 - java.net.http.HttpClient hangs on 204 reply without Content-length 0
Description
While investigating some other bug I noticed that HTTP/1.1 connections where not returned to the pool when the server replied with correct 204 response.
Comments
Fix request (11u) -- will label after testing completed. I would like to downport this for parity with 11.0.9-oracle. I had to do some simple resolves: http://mail.openjdk.java.net/pipermail/jdk-updates-dev/2020-June/003321.html
19-06-2020
This is because the HttpResponse is synthesized directly by the MultiExchange on reception of the response headers. The MultiExchange should notify the ExchangeImpl that no body will be coming so that the ExchangeImpl can take appropriate actions.
14-01-2019