While reading from the file, your are not terminating your loop. So its read all the values and correctly throws EOFException on the next iteration.
use
catch(EOFException e) {
//This isn't problem
}
I know it's an older question, but I had the same issue and managed to reproduce. If the microflow takes 'long' (for example a couple of seconds) and the client closed its browser in the meantime, this "org.eclipse.jetty.io.EofException" may occur. It may take a while before it's in the console log, I think that's because it remains until the session is cleaned.
So, most of the times: being able to reproduce is half of the work of fixing, but I don't think this is fixable, only reduce it by making your microflows run quicker.
You can easily reproduce it by running such a microflow and than close your browser. Then click rerun or stop, such that the session is cleaned up.
This can sometimes occur if data refreshes or you navigate away from a page before it’s completed rendering in the browser.
Does your page refresh periodically, or are there any microflows or nanoflows that refresh data?