On Fri, 8 Mar 2024 06:21:17 GMT, David Holmes <dhol...@openjdk.org> wrote:
>> It may be that once Object.wait is implemented that we can remove the need >> to propagate the interrupt status (there are some TBDs here) so things will >> be a lot simpler. >> >> I think the change here is okay for now but we still have the choice of >> limiting the change to just JVMTI RawMonitorWait. > > Personally I'd prefer to see changes limited to just JVMTI `RawMonitorWait`. > That minimises the risk of any unintended consequences from making the change. I've restored the `InterruptedException` catch in the `Object.wait`. However, the fix in `JavaThread::is_interrupted()` also impacts the variations of `sleep_nanos()`. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/18093#discussion_r1525958712
