简体   繁体   中英

Java + Eclipse: Synchronize stdout and stderr

I use Eclipse. When I have an application like this:

write 20 times 'Hello World\n' to stdout
write 'ERROR\n' to stderr
write 5 times 'Hello  World\n' to stdout

The output looks many times like this:

Hello World
Hello World
Hello World
Hello World
Hello World
Hello World
...
Hello World
Hello World
Hello World
ERROR

Is there a way to synchronize these two output streams? Of course without waiting a few milliseconds after the block of 20 times Hello World and waiting a few milliseconds after printing ERROR .

Believe it or not, flushing is not a solution here....

If a stream leads to "an abstraction provided by the underlying operating system" (eg a disk drive or console) then remaining bytes "are passed to the operating system for writing; it does not guarantee that they are actually written..." (see the OutputStream documentation ). The key here is that the OS can handle flushes from different streams in different orders if it so chooses.

I just had this happen in my program. I had an error message appear between two normal message, both of which had flushed before the error message did.

So the question remains, is there a built-in way to synchronize two streams? Or do we have to handle that manually?

For "serious" use, I prefer not writing directly to System.out/System.err , since it hard-codes the destination, and it also it uses the rather quirky PrintStream (is it a byte stream or a character stream?). If you wrap the output streams in your own PrintWriter , you can then set it to flush automatically - the second argument in the constructor is auto-flush .

Eg

PrintWriter out = new PrintWriter(System.out, true);
PrintWriter err = new PrintWriter(System.err, true);

out.println("Hello world");
//this will flush after writing the end of line

See

System.out和System.err是普通的PrintStream对象(提供flush()方法),因此请尝试System.out.flush()System.err.flush()

AFAIK there is no reliable way to force a sync on 2 unrelated streams.

A workaround is to use only one stream: eg use System.setErr() to redirect out to err, so that everything is printed on the error stream:

System.setErr(System.out);

Or the other way around via System.setOut()

System.setOut(System.err);

A downside of this is that it may change syntax-highlighting: eg some IDEs may highlight text on stderr and stdout differently

Add a flush followed by a Thread.sleep(1) , 99.9% output order will be correct.

For example, this will display as expected.

System.out.println( "stdout 1" ); System.out.flush(); Thread.sleep( 1 );
System.err.println( "stderr 1" ); System.err.flush(); Thread.sleep( 1 );
System.out.println( "stdout 2" ); System.out.flush(); Thread.sleep( 1 );
System.err.println( "stderr 2" ); System.err.flush(); Thread.sleep( 1 );

The only drawback is the sleep for 1 millisecond, ie 1/1000 second

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM