RFR: 8306324: StopThread results in thread being marked as interrupted, leading to unexpected InterruptedException [v3]

Serguei Spitsyn sspitsyn at openjdk.org
Tue Jul 29 09:45:11 UTC 2025


On Mon, 28 Jul 2025 10:50:23 GMT, Alan Bateman <alanb at openjdk.org> wrote:

> It would put the onus on the debugger to interrupt, which I think is the right thing to do. it would remove the interrupt from JavaThread::install_async_exception and would mean no change to JavaThread::sleep_nanos.

Thank you for the suggestion. I've tested it and found that a couple of tests are failed including one JCK test. So, at a minimum this approach is going to be more complicated, it would require a supporting JDI update, consultation with the IDE vendors, CSR and a release note. Also, I kind of share the David's concern above. So, I'm thinking if it is okay to separate this effort from the current fix. I can file an enhancement if it makes sense and worth it.
As I see, the tweak in `JavaThread::sleep_nanos()` is not really needed, so I'll remove it now.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/26365#issuecomment-3131566270


More information about the serviceability-dev mailing list