JDK-8216134 : (process) ProcessBuilder startPipeline does not hide piped streams
- Type: Bug
- Component: core-libs
- Sub-Component: java.lang
- Affected Version: 12
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: windows
- CPU: generic
- Submitted: 2019-01-03
- Updated: 2019-01-15
- Resolved: 2019-01-07
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.
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 13 |
|---|
13 b03Fixed  |
Related Reports
|
Relates :
|
Description
The Windows implementation of ProcessImpl builds the pipeline and correctly pipes the inputs and outputs but the returned Processes do not return the null stream from getInputStream for all but the last process.
The spec for startPipeline says:
"The {@link Process#getInputStream standard output} of all processes
except the last process are null input streams."
A bug in the test hid the problem.