Hi Siba I don't think we need to fix it this way. While the Thread APIs are old they are not obsolete or deprecated. Also, I don't understand how this rewrite using new APIs could be any useful for the bug.
I see another bug JDK-8160596 in the hotspot category was closed as a dup, and I believe your fix won't be able to cover that failure. Since a lot of people believes this is VM or OS related, I'd rather reopen that bug and close yours as a duplicate. Or, you change the category to hotspot. --Max > On Jul 5, 2016, at 8:41 PM, Sibabrata Sahoo <sibabrata.sa...@oracle.com> > wrote: > > Hi, > > Please review the patch for “8079441: Intermittent failures on Windows with > "Unexpected exit from test [exit code: 1080890248]"” > > JBS: https://bugs.openjdk.java.net/browse/JDK-8079441 > Webrev: http://cr.openjdk.java.net/~ssahoo/8079441/webrev.00/ > > Description: > This is a rare failure. It looks to be the test failed due to unexpected exit > of JVM in a Windows machine. Why JVM possibly exit for this test unexpectedly > is unknown. But I thought to provide the fix using recent thread APIs and > that might cause this test to work without such failure in future. The reason > is, > 1) This failure is not intended for the test and is not raised from > Security library. > 2) There are no such test failed in security component in past with same > error which are implemented using new Thread API. > 3) It makes sense to remove using older API and upgrade with new and > retaining the same behavior. > > Thanks, > Siba
