Guidance on troubleshooting org.ldaptive.pool.BlockingConnectionPool issue

Mike Osterman ostermmg at
Mon May 20 16:55:08 EDT 2019

> 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?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the users mailing list