RFR (S) 8048215: [TESTBUG] java/lang/management/ManagementFactory/ThreadMXBeanProxy.java Expected non-null LockInfo

Mandy Chung mandy.chung at oracle.com
Mon Oct 15 17:09:31 UTC 2018

On 10/14/18 9:23 PM, David Holmes wrote:
> bug: https://bugs.openjdk.java.net/browse/JDK-8048215
> webrev: http://cr.openjdk.java.net/~dholmes/8048215/webrev/
> Simple race condition in the test. The main thread does checks that 
> are only valid once the target thread has called o.wait() but there's 
> nothing to ensure that point of execution is reached. The failure is 
> easily reprodcued by just putting in a sleep after:
> Object o = new Object();
> Fix is to add a shared 'waiter' Object that the target waits upon and 
> for which the main also synchronizes on such that the main thread 
> can't proceed until wait() has been called and released the monitor.

Thanks for fixing this.  It's good finds.  This looks good.

I wonder if some other ThreadMXBean tests have similiar bug.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/serviceability-dev/attachments/20181015/d645ff1f/attachment.html>

More information about the serviceability-dev mailing list