RFR: 8316401: sun/tools/jhsdb/JStackStressTest.java failed with "InternalError: We should have found a thread that owns the anonymous lock"

Wed Sep 27 17:27:15 UTC 2023

On Wed, 27 Sep 2023 16:59:17 GMT, Roman Kennke <rkennke at openjdk.org> wrote:

>> I think given this, issuing a warning is the appropriate thing to do. The warning might want to mention that the failure is likely because we are in the middle of a GC. That way the user has some context as to why SA info is not reliable.
>
> Could you advice how such a warning could look like? Does SA use a special stream for that?

Most warnings go to System.err, but I think System.out is better in most cases so the warning appears in line with the rest of the related output. You could do something like:

Warning: We failed to find a thread that owns an anonymous lock. This is likely
due to the JVM currently running a GC. Locking information may not be accurate.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/15907#discussion_r1338959696