Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!ee4no12524775qab.0!news-out.google.com!k2ni4226qap.0!nntp.google.com!ee4no12524769qab.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.java.programmer
Date: Wed, 2 Jan 2013 18:43:33 -0800 (PST)
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=46.7.14.168; posting-account=iOAcbgoAAADC8J1iW-JMMSO74f5TboSg
NNTP-Posting-Host: 46.7.14.168
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <2b4da3ee-0ca3-456d-ae92-5b36e6e1a769@googlegroups.com>
Subject: Recommended way to handle ClosedByInterruptException?
From: raphfrk@gmail.com
Injection-Date: Thu, 03 Jan 2013 02:43:33 +0000
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Xref: csiph.com comp.lang.java.programmer:20908

This is an example of what causes this exception

http://hastebin.com/mayuyuvimu.avrasm

This gives:

Exception in thread "main" java.nio.channels.ClosedByInterruptException
	at java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterrup=
tibleChannel.java:202)
	at sun.nio.ch.FileChannelImpl.map(FileChannelImpl.java:880)
	at Main.main(Main.java:17)

----------------------

Anyway, there doesn't seem to be any sane way of dealing with this.  If int=
errupt is intended to mean stop what you are doing and stop the thread clea=
nly, then this works against that.  This prevents you doing any more writes=
 to the file.  Is the intention that you reopen the file and then do the wr=
ites.

Also, it doesn't even clear the interrupted flag.  So, you have to wipe the=
 flag manually if you want to repeat the write attempt.