JDK-8227738 : jvmti/DataDumpRequest/datadumpreq001 failed due to "exit code is 134"
  • Type: Bug
  • Component: hotspot
  • Sub-Component: jvmti
  • Affected Version: 14
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2019-07-16
  • Updated: 2023-10-03
  • Resolved: 2019-07-17
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 11 JDK 14 JDK 8 Other
11.0.13-oracleFixed 14 b07Fixed 8u401Fixed na,openjdk8u332Resolved
Related Reports
Relates :  
JDK-8225690 - Multiple AttachListener threads can be created
Description
The following test failed due to "exit code is 134":

vmTestbase/nsk/jvmti/DataDumpRequest/datadumpreq001/TestDescription.java

Here's a snippet from the log file:

----------System.out:(9/1690)----------
run [ExecDriver, --java, -agentlib:datadumpreq001=-waittime=5 -verbose=, nsk.jvmti.DataDumpRequest.datadumpreq001]
exec [/scratch/mesos/jib-master/install/jdk-14+6-162/macosx-x64-debug.jdk/jdk-14/fastdebug/bin/java, -XX:MaxRAMPercentage=12, -cp, /scratch/mesos/slaves/a1bab71e-a362-4507-81ed-9c72a04b09cc-S146/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/aff75698-7645-4a7c-9fce-899fade11bae/runs/6faff8e9-fee7-4e29-a6c2-001f738e2821/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jvmti/classes/1/vmTestbase/nsk/jvmti/DataDumpRequest/datadumpreq001/TestDescription.d:/scratch/mesos/slaves/a1bab71e-a362-4507-81ed-9c72a04b09cc-S146/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/aff75698-7645-4a7c-9fce-899fade11bae/runs/6faff8e9-fee7-4e29-a6c2-001f738e2821/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jvmti/classes/1/vmTestbase:/scratch/mesos/slaves/a1bab71e-a362-4507-81ed-9c72a04b09cc-S146/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/aff75698-7645-4a7c-9fce-899fade11bae/runs/6faff8e9-fee7-4e29-a6c2-001f738e2821/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jvmti/classes/1/test/lib, -Djava.library.path=/scratch/mesos/jib-master/install/jdk-14+6-162/macosx-x64-debug.test/hotspot/jtreg/native, -agentlib:datadumpreq001=-waittime=5 -verbose=, nsk.jvmti.DataDumpRequest.datadumpreq001]
- datadumpreq001.cpp, 118: setting event callbacks ...
- datadumpreq001.cpp, 124: setting event callbacks done
enabling JVMTI events ...
- datadumpreq001.cpp, 127: enabling the events done

- datadumpreq001.cpp, 77: waiting for DataDumpRequest event...
Timeout refired 480 times
----------System.err:(18/5077)----------
java.lang.AssertionError: [/scratch/mesos/jib-master/install/jdk-14+6-162/macosx-x64-debug.jdk/jdk-14/fastdebug/bin/java, -XX:MaxRAMPercentage=12, -cp, /scratch/mesos/slaves/a1bab71e-a362-4507-81ed-9c72a04b09cc-S146/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/aff75698-7645-4a7c-9fce-899fade11bae/runs/6faff8e9-fee7-4e29-a6c2-001f738e2821/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jvmti/classes/1/vmTestbase/nsk/jvmti/DataDumpRequest/datadumpreq001/TestDescription.d:/scratch/mesos/slaves/a1bab71e-a362-4507-81ed-9c72a04b09cc-S146/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/aff75698-7645-4a7c-9fce-899fade11bae/runs/6faff8e9-fee7-4e29-a6c2-001f738e2821/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jvmti/classes/1/vmTestbase:/scratch/mesos/slaves/a1bab71e-a362-4507-81ed-9c72a04b09cc-S146/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/aff75698-7645-4a7c-9fce-899fade11bae/runs/6faff8e9-fee7-4e29-a6c2-001f738e2821/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jvmti/classes/1/test/lib, -Djava.library.path=/scratch/mesos/jib-master/install/jdk-14+6-162/macosx-x64-debug.test/hotspot/jtreg/native, -agentlib:datadumpreq001=-waittime=5 -verbose=, nsk.jvmti.DataDumpRequest.datadumpreq001] exit code is 134
	at ExecDriver.main(ExecDriver.java:137)
	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 PropertyResolvingWrapper.main(PropertyResolvingWrapper.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:567)
	at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:127)
	at java.base/java.lang.Thread.run(Thread.java:830)

JavaTest Message: Test threw exception: java.lang.AssertionError: [/scratch/mesos/jib-master/install/jdk-14+6-162/macosx-x64-debug.jdk/jdk-14/fastdebug/bin/java, -XX:MaxRAMPercentage=12, -cp, /scratch/mesos/slaves/a1bab71e-a362-4507-81ed-9c72a04b09cc-S146/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/aff75698-7645-4a7c-9fce-899fade11bae/runs/6faff8e9-fee7-4e29-a6c2-001f738e2821/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jvmti/classes/1/vmTestbase/nsk/jvmti/DataDumpRequest/datadumpreq001/TestDescription.d:/scratch/mesos/slaves/a1bab71e-a362-4507-81ed-9c72a04b09cc-S146/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/aff75698-7645-4a7c-9fce-899fade11bae/runs/6faff8e9-fee7-4e29-a6c2-001f738e2821/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jvmti/classes/1/vmTestbase:/scratch/mesos/slaves/a1bab71e-a362-4507-81ed-9c72a04b09cc-S146/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/aff75698-7645-4a7c-9fce-899fade11bae/runs/6faff8e9-fee7-4e29-a6c2-001f738e2821/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jvmti/classes/1/test/lib, -Djava.library.path=/scratch/mesos/jib-master/install/jdk-14+6-162/macosx-x64-debug.test/hotspot/jtreg/native, -agentlib:datadumpreq001=-waittime=5 -verbose=, nsk.jvmti.DataDumpRequest.datadumpreq001] exit code is 134
JavaTest Message: shutting down test

STATUS:Failed.`main' threw exception: java.lang.AssertionError: [/scratch/mesos/jib-master/install/jdk-14+6-162/macosx-x64-debug.jdk/jdk-14/fastdebug/bin/java, -XX:MaxRAMPercentage=12, -cp, /scratch/mesos/slaves/a1bab71e-a362-4507-81ed-9c72a04b09cc-S146/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/aff75698-7645-4a7c-9fce-899fade11bae/runs/6faff8e9-fee7-4e29-a6c2-001f738e2821/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jvmti/classes/1/vmTestbase/nsk/jvmti/DataDumpRequest/datadumpreq001/TestDescription.d:/scratch/mesos/slaves/a1bab71e-a362-4507-81ed-9c72a04b09cc-S146/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/aff75698-7645-4a7c-9fce-899fade11bae/runs/6faff8e9-fee7-4e29-a6c2-001f738e2821/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jvmti/classes/1/vmTestbase:/scratch/mesos/slaves/a1bab71e-a362-4507-81ed-9c72a04b09cc-S146/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/aff75698-7645-4a7c-9fce-899fade11bae/runs/6faff8e9-fee7-4e29-a6c2-001f738e2821/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jvmti/classes/1/test/lib, -Djava.library.path=/scratch/mesos/jib-master/install/jdk-14+6-162/macosx-x64-debug.test/hotspot/jtreg/native, -agentlib:datadumpreq001=-waittime=5 -verbose=, nsk.jvmti.DataDumpRequest.datadumpreq001] exit code is 134
----------rerun:(30/6310)*----------

There are four failures in this sighting: two on macOSX
and two on Linux-X64; four different machines.
Comments
Changeset: ee70688d Author: Yasumasa Suenaga <ysuenaga@openjdk.org> Date: 2019-07-17 23:22:48 +0000 URL: https://git.openjdk.org/shenandoah-jdk8u/commit/ee70688d83dfc2268f08aadc860c5f7f38ffadff
01-09-2022
Fix Request (8u): Backport to jdk8u. This is a follow-up backport. Low risk. See details in https://mail.openjdk.java.net/pipermail/jdk8u-dev/2021-November/014412.html.
11-11-2021
OK,approving under the assumption that it applies clean and testing shows no regression.
22-07-2021
Fix Request (11u): Required after backport of JDK-8225690. Applies cleanly on top of that one.
21-07-2021
URL: https://hg.openjdk.java.net/jdk/jdk/rev/4888ccfc234e User: ysuenaga Date: 2019-07-17 14:23:15 +0000
17-07-2019
I've sent review request for this issue: https://mail.openjdk.java.net/pipermail/serviceability-dev/2019-July/028731.html It is caused by incorrect handling of AttachListener::is_init_trigger(). This change works fine on serviceability/attach and vmTestbase/nsk/jvmti/DataDumpRequest/datadumpreq001.
16-07-2019
Confirmed it is due to JDK-8225690, and this is the only test that uses ProcessUtils.sendCtrlBreak(). We may want to backout this change, but let's give Yasumasa a chance to have a quick look first.
16-07-2019
I've reproduced this locally. The test sends a ctrl-\ ProcessUtils.sendCtrlBreak() I think this is due to the changes for JDK-8225690, which were pushed yesterday. I'll revert the change locally to verify.
16-07-2019