Re: BufferedWriter cannot handle InterruptedIOException

From:

Tom Anderson <twic@urchin.earth.li>

Newsgroups:

comp.lang.java.programmer

Date:

Sun, 8 Jan 2012 14:12:47 +0000

Message-ID:

<alpine.DEB.2.00.1201081409510.20221@urchin.earth.li>

On Wed, 4 Jan 2012, Jan Burse wrote:

But I think this does not carry over to BufferedOutputStream. I
find the following code there:

   /** Flush the internal buffer */
   private void flushBuffer() throws IOException {
       if (count > 0) {
           out.write(buf, 0, count);
           count = 0;
       }
   }

In case that out throws an InterruptedIOException exception,
the write operation is directly terminated, and the count
is not set to zero.

As an effect next time flushBuffer is called again, the
same bytes are written out again.

What should happen? The field should be set to zero? That means that if
the interruption occurred *before* the bytes got written out, then they
will be lost forever.

The problem with InterruptedIOException, like any IOException, is that
there is no way to know what point in the IO operation it occurred.
Really, at that point, the only safe thing to do is to close the stream
and start again from scratch.

tom

--
music is a interesting thing, DUN COMPARE AND PUT IT TO BLAR BLAR GENRE,
THIS IS A STUPID ACT......MUSIC IS SAME TO EVERYONE -- sihamze