Bug ID: JDK-8204452 SA:serviceability/sa/ClhsdbJstack.java fails with Test ERROR (with -Xcomp=true) java.lang.RuntimeException: Process is still alive. Can't get its output.

Versions (Unresolved/Resolved/Fixed)

The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.

Other
tbd_minorResolved

Test serviceability/sa/ClhsdbJstack.java with following error.
LingeredApp failed to start: java.io.IOException: App waiting timeout
java.lang.RuntimeException: Test ERROR (with -Xcomp=true) java.lang.RuntimeException: Process is still alive. Can't get its output.
	at ClhsdbJstack.testJstack(ClhsdbJstack.java:67)
	at ClhsdbJstack.main(ClhsdbJstack.java:76)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:115)
	at java.base/java.lang.Thread.run(Thread.java:832)
Caused by: java.lang.RuntimeException: Process is still alive. Can't get its output.
	at jdk.test.lib.apps.LingeredApp.getOutput(LingeredApp.java:146)
	at jdk.test.lib.apps.LingeredApp.finishApp(LingeredApp.java:359)
	at jdk.test.lib.apps.LingeredApp.startApp(LingeredApp.java:406)
	at ClhsdbJstack.testJstack(ClhsdbJstack.java:45)
	... 7 more

JavaTest Message: Test threw exception: java.lang.RuntimeException: Test ERROR (with -Xcomp=true) java.lang.RuntimeException: Process is still alive. Can't get its output.
JavaTest Message: shutting down test

STATUS:Failed.`main' threw exception: java.lang.RuntimeException: Test ERROR (with -Xcomp=true) java.lang.RuntimeException: Process is still alive. Can't get its output.

Duplicate of JDK-8197591
03-07-2018
Please see https://bugs.openjdk.java.net/browse/JDK-8205508?focusedCommentId=14191177&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14191177 for a rather lengthy discussion about running with concurrency:8 with dual-VM and triple-VM tests.
28-06-2018
Not sure whether this matters ... In jdk11-jdk.964 failure, tests run on a machine with 16 cores, thus be run as jtreg -concurrency:8 -vmoption:-XX:MaxRAMPercentage=3 (the number is calculated by Makefile at runtime). But I noticed that this machine has 32G mem only, and this testing against fastdebug build with -Xcomp, all these might make tests run "slow" than normal?
28-06-2018
Just another case of insanely slow sparc machines?
28-06-2018
Just another case of insanely slow sparc machines?
28-06-2018
[~mikael] The fix for JDK-8204110 was pushed on June 8. This bug was filed on June 5.
27-06-2018
[~ccheung] Can this be related to https://bugs.openjdk.java.net/browse/JDK-8204110? Seems like the first failure was spotted in roughly the same time frame as that change got pushed..?
27-06-2018
java.io.IOException of LingeredApp should be caused by: 249 public void waitAppReady(long timeout) throws IOException { 250 long here = epoch(); 251 while (true) { 252 long epoch = epoch(); 253 if (epoch - here > (timeout * 1000)) { 254 throw new IOException("App waiting timeout"); 255 } Changing the timeout value should help.
21-06-2018
Happens in more or less every tier3 run.
20-06-2018