JDK-8280233 : Temporarily disable Unix domain sockets in Windows PipeImpl
  • Type: Sub-task
  • Component: core-libs
  • Sub-Component: java.nio
  • Affected Version: 16,17,18
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2022-01-19
  • Updated: 2022-07-19
  • Resolved: 2022-01-19
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 17 JDK 18 JDK 19
17.0.5Fixed 18 b33Fixed 19Fixed
Related Reports
Relates :  
JDK-8279916 - Reading from Pipe may hang on Windows
Description
Pending full investigation of the cause of the parent issue (JDK-8278369) this sub-task will disable the use of Unix domain sockets in the Windows Pipe implementation, reverting to the previous (pre JDK 16) TCP socket impl. This impl was always used in versions of windows other than 10, 2019 server+ that didn't support Unix domain sockets.

It's expected the Unix domain impl will be restored later, and UNIX protocol family SocketChannel/ServerSocketChannel still work.
Comments
In the case of JDK-8279916 that was Zulu Free customer complaint about exactly 16. I can check if they are going to use 17. Upd: MS guy also told that the root cause problem is too complex and won't be resolved soon, and if it even gets solved then persistent fix still will have to disable Unix domain sockets conditionaly depending on Winsock version. P.S.: in spite of the fact that it was hard to create a stable reproducer the case is not artifical. That is just a race inside Winsock library, and any application using pipes has a chance to get stalled on Windows.
19-07-2022
Hi Alexey, has there been any indication this happens in real applications? Was there an issue raised from an end-user? I only find this caused some test failures so far, but it is live since the release of 16. So I'm not sure it is required to disable Unix domain sockets in 17. Best regards, Goetz
19-07-2022
Fix request (17u) The patch is to be backported to 17u-dev because it is affected as well. The original patch is applied cleanly
13-07-2022
A pull request was submitted for review. URL: https://git.openjdk.org/jdk17u-dev/pull/548 Date: 2022-07-13 12:33:05 +0000
13-07-2022
Changeset: 03680bea Author: Michael McMahon <michaelm@openjdk.org> Date: 2022-01-19 19:48:37 +0000 URL: https://git.openjdk.java.net/jdk18u/commit/03680bea1cca1113ea23a1eb7a413b93dd73c381
25-01-2022
Changeset: 03680bea Author: Michael McMahon <michaelm@openjdk.org> Date: 2022-01-19 19:48:37 +0000 URL: https://git.openjdk.java.net/jdk18/commit/03680bea1cca1113ea23a1eb7a413b93dd73c381
19-01-2022
A pull request was submitted for review. URL: https://git.openjdk.java.net/jdk18/pull/109 Date: 2022-01-19 10:01:38 +0000
19-01-2022