-
Sub-task
-
Resolution: Fixed
-
P4
-
None
-
b09
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8291900 | 17.0.5 | Christoph Langer | P4 | Resolved | Fixed | b02 |
Observations also show that no data is being lost due to the bug. i.e. even when one of the channels is closed all data is correctly sent and received. It is just the close notification that seems to get lost. That suggests the usage in the selector notification mechanism will not be affected.
Unix domain sockets will otherwise remain disabled in the Windows public Pipe implementation until the windows issue is fixed.
- backported by
-
JDK-8291900 Enable Unix domain sockets in Windows Selector notification mechanism
- Resolved
- relates to
-
JDK-8282296 (se) Pipe.open() creates a Pipe implementation that uses Unix domain sockets (win)
- Resolved
-
JDK-8280868 LineBodyHandlerTest.java creates and discards too many clients
- Resolved
-
JDK-8295275 java/net/httpclient/ProxyAuthDisabledSchemes.java failed with "IOException: Unable to establish loopback connection"
- Closed
-
JDK-8266900 java/net/httpclient/ShortResponseBody.java fails on windows with java.io.IOException: Unable to establish loopback connection
- Closed
- links to
-
Commit openjdk/jdk17u-dev/b2848515
-
Commit openjdk/jdk/87ab0994
-
Review openjdk/jdk17u-dev/625
-
Review openjdk/jdk/7302