8330363: JDI ThreadDeathEvent/thread/thread001 timed out with UT enabled

[plummercj]

After receiving the expected 4 ThreadDeathEvents, the test disables the ThreadDeathRequest and stops processing events. However, there is already another ThreadDeathEvent in flight for the UsageTracker thread. That results in suspending all debuggee threads, with the expectation that the debugger will eventually process the event and do an eventSet.resume(). That never happens, leaving the debuggee suspended while the debugger waits for the debuggee to send a DONE command, which it can't because it is suspended.

After disabling the ThreadDeathRequest, the debuggee needs to make sure all pending events get processed.

Tested by running thread001 about 600 times with JTREG_USAGE_TRACKER=true

---

• I confirm that I make this contribution in accordance with the OpenJDK Interim AI Policy.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8330363: JDI ThreadDeathEvent/thread/thread001 timed out with UT enabled (Bug - P4)

Reviewers

• Serguei Spitsyn (@sspitsyn - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/31156/head:pull/31156
$ git checkout pull/31156

Update a local copy of the PR:
$ git checkout pull/31156
$ git pull https://git.openjdk.org/jdk.git pull/31156/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 31156

View PR using the GUI difftool:
$ git pr show -t 31156

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/31156.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back cjplummer! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@plummercj This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8330363: JDI ThreadDeathEvent/thread/thread001 timed out with UT enabled

Reviewed-by: sspitsyn

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 100 new commits pushed to the master branch:

• b9778cc: 8383631: Test vmTestbase/nsk/jdb/kill/kill003/kill003.java failed - possible NullPointerException
• 125cffd: 8382273: Update nsk/jvmti/unit tests to use ThreadWrapper
• bcbf5cf: 8383354: Update LCMS to 2.19.1
• ... and 97 more: https://git.openjdk.org/jdk/compare/8480d12c6f1970587c31d69c0f218bda0da4a4f9...master

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[openjdk]

@plummercj The following label will be automatically applied to this pull request:

• serviceability

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 00: Full (81729a18)

[sendaoYan]

Hi, what does JTREG_USAGE_TRACKER=true mean to. I can't find the related documents.

[plummercj]

Hi, what does JTREG_USAGE_TRACKER=true mean to. I can't find the related documents.

I think that's something that is only supported internally at Oracle. It runs the test with UsageTracker enabled. This frequently causes issues with JDI tests that track ThreadStart and ThreadDeath events because running with UsageTracker enabled results in the UsageTracker thread starting and exiting while the test is running.

[sspitsyn]

It looks reasonable.