Integrated: 8293445: clhsdb "thread" command gives incorrect error message for bad threadID
Chris Plummer
cjplummer at openjdk.org
Tue Sep 6 22:30:51 UTC 2022
On Tue, 6 Sep 2022 19:28:15 GMT, Chris Plummer <cjplummer at openjdk.org> wrote:
> As pointed out in [JDK-8283010](https://bugs.openjdk.org/browse/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".
>
> I'd like to push this as a trivial change.
This pull request has now been integrated.
Changeset: 710a1434
Author: Chris Plummer <cjplummer at openjdk.org>
URL: https://git.openjdk.org/jdk/commit/710a14347344f3cc136f3b7f41aad231fbe43625
Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod
8293445: clhsdb "thread" command gives incorrect error message for bad threadID
Reviewed-by: dcubed
-------------
PR: https://git.openjdk.org/jdk/pull/10186
More information about the serviceability-dev
mailing list