Stream closed exception on Java 1.8 when piping input stream about zt-exec HOT 5 CLOSED

Thanks for reporting this. I pushed a fix.
You can try it if you build the latest code on your machine.
I'm probably going to release 1.9 also soon.

from zt-exec.

@reinra Thank you for the quick reply! I've learned some things in the meantime.

We just determined that this is some kind of race condition, as opposed to a 100%-reproducible bug. If you use a script like this:

#!/usr/bin/env sh

exit 0

instead of calling /bin/true directly, the exception seems to be thrown significantly less frequently. This leads me to believe that some of the overhead of running the env command and starting another sh in the script above causes some background processing in the JDK to be more likely to have completed before the process exits, and somehow this prevents the exception from being triggered.

from zt-exec.

It makes sense as this error only occurred if JVM couldn't flush the buffer to forked process' stdin before the process was closed. If the process runs longer there's enough time to write into the stdin.

from zt-exec.

Seems like issue wrongly closed.
Because there are no ability to communicate with process STDIN. Original OutputStream is closed here. ProcessExecutor want to work only with PumpStreamHandler, looks like interface ExecuteStreamHandler useless in streams(ExecuteStreamHandler). Moreover PumpStreamHandler recreated by ProcessExecutor few times basing on streams from previous PumpStreamHandler.

Helps only custom inheritor of PumpStreamHandler with executing ProcessExecutor without readOutput, redirectOutput, etc. and with streams(customHandler). But in this case library profit goes to zero.

from zt-exec.

communicate

I mean exactly "communication", i.e. read process STDOUT and write into its STDIN continuously.

from zt-exec.