Please find below a changeset to address: 8130649: java/util/logging/LoggingDeadlock2.java times out https://bugs.openjdk.java.net/browse/JDK-8130649
The proposed changeset doesn't fix the issue but instruments the test a bit more so that we can get a clue of what is happening. http://cr.openjdk.java.net/~dfuchs/webrev_8130649/webrev.00/ When a test fails in timeout, jtreg obtains a Thread Dump before killing it. However - in our case - that thread dump is quite uninteresting - because the real test is performed in a subprocess - and that's where bad things could be happening. The proposed instrumentation will try to obtain a thread dump of the subprocess after a sensible time (60secs) but before the jtreg timeout kicks in (default jtreg timeout should be about 120sec x time factor - if I remember well). best regards, -- daniel
