JDK-8205654 : serviceability/dcmd/framework/HelpTest.java timed out
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc
  • Affected Version: 11
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2018-06-26
  • Updated: 2022-09-02
  • Resolved: 2019-02-08
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 13
11.0.18-oracleFixed 13 b08Fixed
Related Reports
Duplicate :  
Duplicate :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Description
serviceability/dcmd/framework/HelpTest.java timed out. This looks very similar to JDK-8166642, which was fixed. The test got through the HelpTest.file() and HelpTest.jmx() sections, but the HelpTest.mainClass() section issued its jcmd and never received any output, nor did it complete.


Comments
Fix request (11u): This fixes an issue with jcmd that is demonstrated intermittently by a failing test case "serviceability/dcmd/framework/HelpTest.java". It looks like a nice bug fix and will stabilize the test environment. I had to add some manual modifications to the original patch so I started a review thread: https://mail.openjdk.java.net/pipermail/jdk-updates-dev/2019-July/001459.html After the fix, the test issue seems to disappear. No other regressions shown.
23-07-2019

URL: http://hg.openjdk.java.net/jdk/jdk/rev/67537bbafd7f User: dtitov Date: 2019-02-08 17:43:02 +0000
08-02-2019

The proposed fix didn't help. Additional tracing showed that when jcmd is invoked with the main class name it iterates over all running Java processes and temporary attaches to them to retrieve the main class name. It hangs while trying to attach to one of the running Java processes. There are numerous Java processes running at the host machine some associated with the test framework itself and another with the tests running in parallel. It is not clear what exact is this particular process since the jcmd hangs before retrieving the process' main class name, but after all tests terminated the process with this id is no longer running.
29-11-2018

We are seeing the same issue in our nightly testing at Twitter.
03-07-2018