JDK-8197591 : Tests failing with App waiting timeout
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc-agent
  • Affected Version: 10,11,12,13
  • Priority: P3
  • Status: Resolved
  • Resolution: Cannot Reproduce
  • OS: generic
  • CPU: generic
  • Submitted: 2018-02-12
  • Updated: 2021-04-11
  • Resolved: 2020-04-11
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.
JDK 15
15Resolved
Related Reports
Duplicate :  
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.
Duplicate :  
JDK-8197592 - Test serviceability/sa/ClhsdbJstack.java failed with App waiting timeout
Duplicate :  
JDK-8194848 - SA: serviceability/sa/TestHeapDumpForLargeArray.java - java.io.IOException: App waiting timeout
Relates :  
JDK-8197590 - Test serviceability/dcmd/gc/HeapDumpAllTest.java - Agent timeout
Relates :  
JDK-8194848 - SA: serviceability/sa/TestHeapDumpForLargeArray.java - java.io.IOException: App waiting timeout
Relates :  
JDK-8265037 - serviceability/sa/ClhsdbPmap.java#id1 failed with "RuntimeException: Process is still alive. Can't get its output."
Relates :  
JDK-8215042 - Umbrella bug for all SA failures in tier1
Description
Test failed: 


----------System.err:(22/1938)----------
Command line: ['/scratch/opt/mach5/mesos/work_dir/jib-master/install/jdk12-jdk.39/solaris-sparcv9-debug.jdk/jdk-12/fastdebug/bin/java' '-Xcomp' '-cp' '/scratch/opt/mach5/mesos/work_dir/0a9b156e-0af8-49a6-a644-304b366c3832/testoutput/jtreg/JTwork/classes/3/serviceability/sa/ClhsdbFindPC.d:/scratch/opt/mach5/mesos/work_dir/0a9b156e-0af8-49a6-a644-304b366c3832/testoutput/jtreg/JTwork/classes/3/test/lib' 'jdk.test.lib.apps.LingeredApp' '0a3944fa-904d-4d1e-ab02-e00ba43c2691.lck' ]
LingeredApp failed to start: java.io.IOException: App waiting timeout
java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: Process is still alive. Can't get its output.
	at ClhsdbFindPC.testFindPC(ClhsdbFindPC.java:95)
	at ClhsdbFindPC.main(ClhsdbFindPC.java:103)
	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:834)
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 ClhsdbFindPC.testFindPC(ClhsdbFindPC.java:46)
	... 7 more

JavaTest Message: Test threw exception: java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: Process is still alive. Can't get its output.
Comments
LingeredApp has been already improved by other fixes, further minor improvements are not related to this failures
11-04-2020
There is no failures like this for a long time, but look like LingeredApp can be improved in the area.
13-03-2020
Failed on JDK 13 also: ----------System.err:(19/1415)---------- Command line: ['/scratch/export/home/aginfra/muneer/jtest/jdks/jdk-13/bin/java' '-XX:+UsePerfData' '-Xmx8g' '-cp' '/scratch/export/home/aginfra/muneer/jtest/results13/3/hotspot/JTwork/classes/3/serviceability/sa/TestHeapDumpForLargeArray.d:/scratch/export/home/aginfra/muneer/jtest/results13/3/hotspot/JTwork/classes/3/test/lib' 'LingeredAppWithLargeArray' 'e86a2092-0432-445d-a949-610d9549bb83.lck' ] LingeredApp stdout: []; LingeredApp stderr: [] LingeredApp exitValue = 0 java.io.IOException: App waiting timeout at jdk.test.lib.apps.LingeredApp.waitAppReady(LingeredApp.java:258) at jdk.test.lib.apps.LingeredApp.startApp(LingeredApp.java:430) at TestHeapDumpForLargeArray.main(TestHeapDumpForLargeArray.java:106) 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:567) at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:127) at java.base/java.lang.Thread.run(Thread.java:835) JavaTest Message: Test threw exception: java.io.IOException: App waiting timeout JavaTest Message: shutting down test STATUS:Failed.`main' threw exception: java.io.IOException: App waiting timeout
11-01-2019
Might fail also in tier1: http://java.se.oracle.com:10065/mdash/jobs/lmesnik-hs-tier1-12-8-20180826-0140-36088/tasks/naHeXbB9Zb/results?search=status:overview
30-08-2018
The following test failed in the JDK12 CI: serviceability/sa/TestHeapDumpForLargeArray.java Here is a snippet of the log file: ----------System.out:(0/0)---------- ----------System.err:(19/1438)*---------- Command line: ['C:\\ade\\mesos\\work_dir\\jib-master\\install\\jdk12-jdk.99\\windows-x64-debug.jdk\\jdk-12\\fastdebug/bin/java' '-XX:+UsePerfData' '-Xmx8g' '-XX:MaxRAMPercentage=6' '-cp' 'T:\\testoutput\\jtreg\\JTwork\\classes\\3\\serviceability\\sa\\TestHeapDumpForLargeArray.d;T:\\testoutput\\jtreg\\JTwork\\classes\\3\\test\\lib' 'LingeredAppWithLargeArray' '0b60ff65-653a-4485-92f8-f8a3e74cd664.lck' ] LingeredApp stdout: []; LingeredApp stderr: [] LingeredApp exitValue = 0 java.io.IOException: App waiting timeout at jdk.test.lib.apps.LingeredApp.waitAppReady(LingeredApp.java:254) at jdk.test.lib.apps.LingeredApp.startApp(LingeredApp.java:426) at TestHeapDumpForLargeArray.main(TestHeapDumpForLargeArray.java:104) 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:834) JavaTest Message: Test threw exception: java.io.IOException: App waiting timeout JavaTest Message: shutting down test STATUS:Failed.`main' threw exception: java.io.IOException: App waiting timeout ----------rerun:(42/5398)*----------
20-07-2018
If this is targetted to 12 then we need to exclude the failing test on Solaris-sparc.
27-02-2018
Updated JDK-8197590, it does not use LingeredApp. Also the failure of the LingeredApp itself is because the process launched using ProcessBuilder pb = new ProcessBuilder(cmd); appProcess = pb.start(); doesn't seem to be starting.
21-02-2018
Also see JDK-8197590 , which involves a jcmd failure in the same test run as a couple of the above failures.
12-02-2018
See JDK-8194848 and JDK-8080041. This seems to be an issue that pops up with various sa tests that use LingerApp. So far it has always been on Solaris-sparc.
12-02-2018