Hi Daniel, On Thu, 2019-03-14 at 11:24 +0000, Daniel Fuchs wrote: > Hi Severin, > > If you can update WAIT_FOR_JMX_AGENT_TIMEOUT_MS in > JMXAgentInterfaceBinding.java > to 20000, in you webrev.04, then I believe you should > be good to go and push the changes. > > This seems to fix the instability I had observed with > fastdebug VMs.
Great! It works fine for me on my box now too. 100 iterations no failure. I'm going to push it. Thanks again for your help! Thanks, Severin > > best regards, > > -- daniel > > On 12/03/2019 18:22, Daniel Fuchs wrote: > > > This is what I have tried: > > > http://cr.openjdk.java.net/~sgehwolf/webrevs/JDK-8219585/04/webrev/ > > > > > > If you think we should try this one. That's fine with me. > > > > I have now also tested webrev.04 with a test config that uses > > the fastdebug VM and observed many intermittent failures. > > The logs let me think that maybe the JMX agent needed to be > > given more time to come up: > > > > So I am now experimenting with your webrev.04 above - but with the > > following additional change to JMXAgentInterfaceBinding.java: > > > > private static final int WAIT_FOR_JMX_AGENT_TIMEOUT_MS = > > 20000; > > > > So far the result are looking better, but tests are still running. > > I wonder whether the same change would also reduce the number of > > intermittent failures on your box? > > > > best regards, > > > > -- daniel
