[logback-user] Logback suddenly stopped logging

[Robert Elliot]

> Given that the issue is Solaris-specific and preventable with the
> -XX:-UseVMInterruptibleIO option, and given that the programming style
> for thread synchronization using interrupt() is in my opinion quite
> lame, I am tempted to ignore this issue. However, it is also true that
> some classes belonging to the JDK, i.e. PrintStream, invoke
> Thread.interrupt() after catching an InterruptedIOException. It
> follows that calling Thread.interrupt() looks like the sanctioned
> coding style.

My understanding from reading Java Concurrency in Practice (pp 92-94 and 138-144) is that it is more than sanctioned coding style - it's vital to correct working of the interrupted thread model, and a well behaved consumer of InterruptedException must restore the interrupted status unless it is going to propagate the exception or is sure that the thread will terminate immediately after catching it.