This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: [PATCH] for Review: SelectorImpl.wakeup() + Synchronization
- From: Michael Koch <konqueror at gmx dot de>
- To: Mohan Embar <gnustuff at thisiscool dot com>
- Cc: Michael Koch <konqueror at gmx dot de>, GCJ Patches <java-patches at gcc dot gnu dot org>
- Date: Fri, 19 Dec 2003 17:54:06 +0100
- Subject: Re: [PATCH] for Review: SelectorImpl.wakeup() + Synchronization
- References: <20031219163134.GF16362@mail.konqueror.de> <75ICGD1YWR97JD61UREAB8LYUA7PM54.3fe32b5c@p733>
On Fri, Dec 19, 2003 at 10:46:20AM -0600, Mohan Embar wrote:
> Hi Michael,
>
> >Please read the documentation of AbstractSelector.end() and you will
> >see. I think the same applies to AbstractInterruptableChannel.end().
>
> >They throw exceptions if the select (or another blocking IO operation)
> >was interrupted somehow.
>
> Nope. AbstractSelector.end() doesn't throw any exceptions. Selector.select()
> shouldn't throw exceptions with thread interruption.
Damn, only AbstractInterruptibleChannel.end() throws this exceptions.
> Reading the JavaDoc, I think I see how they want us to implement interruption,
> but I think they way we've implemented interruptible I/O on POSIX and Win32
> precludes us from doing this and forces us to do the inverse: that wakeup()
> uses Thread.interrupt() under the covers.
I think I need to dig into chaos some time soon.
Michael