Path: csiph.com!usenet.pasdenom.info!news.albasani.net!.POSTED!not-for-mail From: Jan Burse Newsgroups: comp.lang.java.programmer Subject: Re: Interrupted exception chaining Date: Tue, 25 Sep 2012 23:55:25 +0200 Organization: albasani.net Lines: 38 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: news.albasani.net j+wi3MmHamPo4b6KrLzldpCoVXvaReLwXZQ4FcW6y6uOxrQ59ql0OHGekZkZJ8LKpomPwXzzMfTPkVbp0lcTP6e6pB1YanEQ1X35GtetP7s461kRTUYKXmQ17sYrLult NNTP-Posting-Date: Tue, 25 Sep 2012 21:55:25 +0000 (UTC) Injection-Info: news.albasani.net; logging-data="hh9vGmYWeKBLy/MpcODX9nUaX8IUyY0rdscKZo815OE9u9CeTp0bPySO34SbO1Us75I3sw7Hd/mIvsBZC2jZLudBZvenYJi1XHCbNmCnLf0ThJ6clZCi9TUuf/Df6r0M"; mail-complaints-to="abuse@albasani.net" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120909 Firefox/15.0.1 SeaMonkey/2.12.1 In-Reply-To: Cancel-Lock: sha1:y8e1/W9lSP2tn3bYNZsLo7mkUmo= Xref: csiph.com comp.lang.java.programmer:18930 But the programming pattern for awaitUninterruptibly() would be different from uninterruptableWait(). Since the spec says that spurious wakeups are still posible. So I guess something along: while (!(flag=Thread.interrupted()) && !) awaitUninterruptibly(); if (!flag) } else { Thread.currentThread().interrupt(); } Ugly Jan Burse schrieb: > Hi, > > markspace schrieb: >> I don't see how "done" can be reliably reset. There's going to be a >> race condition somewhere. Might as well use ReetrantLock, it solves >> this problem. > > Do you refer to: > > Condition.awaitUninterruptibly() ? > http://docs.oracle.com/javase/1.5.0/docs/api/java/util/concurrent/locks/Condition.html#awaitUninterruptibly%28%29 > > > Didn't look yet at the source. What is the design? > > Bye > > > >