Guidance on troubleshooting org.ldaptive.pool.BlockingConnectionPool issue

[Mike Osterman]

>
> 'kill' is a 'nix command. You want the thread dump from the jvm that is
> running jetty.
>

Correct, it is a 'nix command, but sending a "QUIT" (-3) signals the JVM to
perform a thread dump. It doesn't actually terminate the process (which
makes "QUIT" kind of a misnomer):
https://github.com/irockel/tda/wiki/02.-Request-Thread-Dumps

You could try visualvm.
>

Thanks! I'll take a look at this.

I did manage to get a thread dump when in the "bad" state using this
command:
sudo -u shibidp jstack [PID] > threaddump.log

The trick now is interpreting it. Would it make sense to create a Jira
issue and upload the dump file at this point? I've given it a pretty
thorough look over, but nothing's standing out to me.

Thanks,
Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20190521/ad3fec2a/attachment.html>