Welcome to OStack Knowledge Sharing Community for programmer and developer-Open, Learning and Share
Welcome To Ask or Share your Answers For Others

Categories

0 votes
348 views
in Technique[技术] by (71.8m points)

java - Why does reading from Process' InputStream block altough data is available

Java:

Process p = Runtime.getRuntime().exec("myCommand");
final InputStream in = p.getInputStream();

new Thread()
{
    public void run()
    {
        int b;
        while ((b = in.read()) != -1) // Blocks here until process terminates, why?
            System.out.print((char) b);
    }
}.start();

CPP:

#include <stdio.h>
#include <unistd.h>

int main(int argc, char** argv)
{
    printf("round 1
");

    // At this point I'd expect the Java process be able
    // to read from the input stream.

    sleep(1);

    printf("round 2
");

    sleep(1);

    printf("round 3
");

    sleep(1);

    printf("finished!
");

    return 0;

    // Only now InputStream.read() stops blocking and starts reading.
}

The documentation of InputStream.read() states:

This method blocks until input data is available, the end of the stream is detected, or an exception is thrown.

And yes, I'm aware of this (thus linux related?):

java.lang.Process: Because some native platforms only provide limited buffer size for standard input and output streams, failure to promptly write the input stream or read the output stream of the subprocess may cause the subprocess to block, or even deadlock.

My questions are:

  1. Why is InputStream.read() blocking although I should already have data available right after the process starts? Am I missing something on either side?

  2. If it's linux related, is there any way to read from the process' output stream without blocking?

See Question&Answers more detail:os

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome To Ask or Share your Answers For Others

1 Answer

0 votes
by (71.8m points)

Why does reading from Process' InputStream block although data is available

It doesn't. The problem here is that data isn't available when you think it is, and that's caused by buffering at the sender.

You can overcome that with fflush() as per @MarkkuK.'s comment, or by telling stdio not to buffer stdout at all, as per yours.


与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome to OStack Knowledge Sharing Community for programmer and developer-Open, Learning and Share
Click Here to Ask a Question

...