Guidance on troubleshooting org.ldaptive.pool.BlockingConnectionPool issue

[Mike Osterman]

All, I wanted to report back to the list that after throwing up my hands
and DOUBLING the -xmx (8GB instead of 4GB, which was the highest documented
memory allocation I could find), the trouble has not returned. When in
doubt, add more RAM.

My working theory is that it was a function of not enough available and
collision of garbage collection and the InCommon metadata refresh. Again,
it's just a theory.

I'm looking forward to the per-entity MDQ. :)

-Mike

On Thu, May 23, 2019 at 1:20 PM Daniel Fisher <dfisher at vt.edu> wrote:

> On Tue, May 21, 2019 at 10:39 PM Mike Osterman <ostermmg at whitman.edu>
> wrote:
>
>> 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.
>>
>
> You can create a JIRA issue or send it directly to me. I should have time
> to look at it next week.
>
> --Daniel Fisher
>
> --
> For Consortium Member technical support, see
> https://wiki.shibboleth.net/confluence/x/coFAAg
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20190726/73d16180/attachment.html>