Random printing order for System.out & System.err calls [duplicate]

Answer 1

This has already been answered here:

Java: System.out.println and System.err.println out of order

This happens because your finally clause is using System.out and the other code is using System.err. The err stream is flushing out prior to the out stream or vice versa.

As a result, the order of printed data will not be guaranteed to come out in the same order that it is called.

You can always have your console direct the err stream to a file or the out stream to a file for later inspection. Or, change your code to print everything to System.out. Many programmers do not use err and the usefulness is debatable unless you capture err separate from the console.

Just use out!

Over and out...

Answer 2

Because System.out and System.err are both pointing to the console in your case.

To demonstrate, if you add System.out.flush() and System.err.flush() after println(), then the output will be consistant.

Answer 3

I believe this is because you are writing to two different outputs (one is standard out and the other standard error). These are probably handled by two different threads at runtime to allow writing to both during java execution. Assuming this is the case, the cpu task scheduler is not going to execute the threads in the same order every time.

You should never get this functionality if all of your output is going to the same output stream (ie everything goes to standard out or everything goes to standard err). You will never be guaranteed execution order of standard error vs standard output.