<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="text-align:left; direction:ltr;">
<div>Mike,</div>
<div><br>
</div>
<div>'kill' is a 'nix command. You want the thread dump from the jvm that is running jetty.</div>
<div>You could try visualvm.</div>
<div><br>
</div>
<div>Ray</div>
<div><br>
</div>
<div>On Mon, 2019-05-20 at 13:55 -0700, Mike Osterman wrote:</div>
<blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">
<div dir="ltr">
<div dir="ltr">
<div class="gmail_quote">
<blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div class="gmail_quote">
<div>I don't believe we have any JVM core dumps. I'm assuming we'd need to generate it when in the midst of the pegged CPU condition? If so, is that the "kill -3" technique or something else?</div>
</div>
</div>
</div>
</div>
<br>
</blockquote>
<div><br>
</div>
<div>I missed another opportunity to collect info during a lockup as I tried a "kill -3" and found that didn't dump any info anywhere that I could find. After digging around some more, I found that with Tomcat, that would show up in catalina.out, but we're
running on Jetty. The Jetty log dir was empty.</div>
<div><br>
</div>
<div>I searched some more, and I think I found that this would work for Jetty:</div>
<div>sudo -u shibidp jstack [PID] > threaddump.log</div>
<div><br>
</div>
<div>Any additional pointers on getting a useful thread dump? Ideas on where "kill -3" might have dropped its data?</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Mike</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
</div>
</blockquote>
<div><span>
<pre>-- <br></pre>
<div>Ray Bon</div>
<div>Programmer Analyst</div>
<div>Development Services, University Systems</div>
<div>2507218831 | CLE 019 | rbon@uvic.ca</div>
</span></div>
</body>
</html>