<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">On 03/04/2025 10:13, 唐佳未(佳未) wrote:<br>
</div>
<blockquote type="cite" cite="mid:3d05a494-d726-4aea-a413-c5f76529a770.tjw378335@alibaba-inc.com">
<div class="__aliyun_email_body_block">
<div style="font-family: Tahoma, Arial, STHeitiSC-Light, SimSun">
<div style="clear: both; font-family: Tahoma, Arial, STHeitiSC-Light, SimSun;"><span>I
think it may be useful to add a tool which can print more
information about the unmounted virtual threads after the
JEP491.</span></div>
<div style="clear: both; font-family: Tahoma, Arial, STHeitiSC-Light, SimSun;"><span><br>
</span></div>
<div style="clear: both; font-family: Tahoma, Arial, STHeitiSC-Light, SimSun;">I
knew that the`jcmd <span>Thread.dump_to_file` cmd could
generate a json/text file to give a view of the all the
threads and virtual threads but it lacks information about
the locks after JEP491.</span></div>
</div>
</div>
</blockquote>
<br>
There is work in progress to update the existing command to include
lock information. So it would be both the plain text and JSON object
formats. I think this would be better than introducing yet another
command that is plain text only.<br>
<br>
-Alan<br>
<br>
</body>
</html>