Guidance on troubleshooting org.ldaptive.pool.BlockingConnectionPool issue
rbon at uvic.ca
Tue May 21 13:36:41 EDT 2019
'kill' is a 'nix command. You want the thread dump from the jvm that is running jetty.
You could try visualvm.
On Mon, 2019-05-20 at 13:55 -0700, Mike Osterman wrote:
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?
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.
I searched some more, and I think I found that this would work for Jetty:
sudo -u shibidp jstack [PID] > threaddump.log
Any additional pointers on getting a useful thread dump? Ideas on where "kill -3" might have dropped its data?
Development Services, University Systems
2507218831 | CLE 019 | rbon at uvic.ca
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users