RFR: JDK-6546236 Thread interrupt() of Thread.sleep() can be lost on Solaris due to race with signal handler

Chris Hegarty chris.hegarty at oracle.com
Tue Feb 11 01:25:44 PST 2014

On 11 Feb 2014, at 09:14, Alan Bateman <Alan.Bateman at oracle.com> wrote:

> On 11/02/2014 08:59, Frederic Parain wrote:
>> Alan,
>> Thank you for the clarification.
>> There's still a bit of clean up required on the JDK
>> side. Three tests have hard coded usage of the
>> UseVMInterruptibleIO flag:
>> jdk/test/java/nio/file/Files/InterruptCopy.java
>> jdk/test/java/util/concurrent/ThreadPoolExecutor/ThrowingTasks.java
>> jdk/test/java/util/concurrent/BlockingQueue/Interrupt.java

I don't see why these concurrency tests set that VM option. I think it can simply be removed. Maybe they did need interruptible IO at one point, but have since been refactored.


>> Even if those tests force the flag to false, they
>> will fail with "Unrecognized VM option" as soon as
>> the UseVMInterruptibleIO goes away.
> I removed -XX:-UseVMInterruptibleIO from a number of jdk tests in JDK 8 and I think these are the only 3 remaining. I can get these sorted out in jdk9/dev now if it would help.
> -Alan.

More information about the hotspot-runtime-dev mailing list