Re: Interrupted exception chaining

From:

Daniele Futtorovic <da.futt.news@laposte-dot-net.invalid>

Newsgroups:

comp.lang.java.programmer

Date:

Wed, 26 Sep 2012 01:43:07 +0200

Message-ID:

<k3tfih$3q5$1@dont-email.me>

On 25/09/2012 12:25, raphfrk@gmail.com allegedly wrote:

Is there a recommended way of "chaining" interrupted exceptions?

This is to implement a method call that doesn't throw an interrupted exception, but which calls a method which can be interrupted.

public void uninterruptableWait(Object c) {
    boolean done = false;
    boolean interrupted = false;
    synchronized (c) {
        while (!done) {
            try {
                c.wait();
                done = true;
            } catch (InterrupedException ie) {
                interrupted = true;
            }
        }
    }
    if (interrupted) {
        Thread.currentThread().interrupt();
    }
}

If that interrupt was unexpected, and causes a stack trace, then it would be nice if it could include the details from the thrown exception.

Is there a better way to do the above?

a) When catching an InterruptedException, always, always call
Thread.currentThread().interrupt() in the catch block. Always. Unless
you know what you're doing.

b) If you want a stacktrace, just print a stacktrace. Like, in the catch
block. But note that by definition, interruptedness is a state, not an
action. The only thing a stacktrace will tell you is where in the code
that state was /checked/, not where it was /set/.

--
DF.