JDK-8293445 : clhsdb "thread" command gives incorrect error message for bad threadID
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc-agent
  • Affected Version: 20
  • Priority: P5
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2022-09-06
  • Updated: 2022-09-12
  • Resolved: 2022-09-06
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 20
20 b14Fixed
Related Reports
Relates :  
Description
As pointed out in JDK-8283010, when a bad threadID is passed to the clhsdb "thread" command, the error message is incorrect:

hsdb> thread 18
Couldn't find thread thread

It should say "thread 18", not "thread thread". The code looks like:

                        out.println("Couldn't find thread " + name);

"name" is the name of the command. It should instead use "id". 
Comments
Changeset: 710a1434 Author: Chris Plummer <cjplummer@openjdk.org> Date: 2022-09-06 22:26:29 +0000 URL: https://git.openjdk.org/jdk/commit/710a14347344f3cc136f3b7f41aad231fbe43625
06-09-2022

A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/10186 Date: 2022-09-06 19:28:15 +0000
06-09-2022