I ended up going with poolPassivator=BIND, based on the findings of Carlos Fernandez in the thread. Apparently as long as you are using a bindDn and bindCredential (as opposed to direct authentication) this works. I can confirm that it seems to have cleared up the issue we had been seeing.
Tim On 17-07-11, 07:28, "[email protected] on behalf of Tom Poage" <[email protected] on behalf of [email protected]> wrote: > On Jul 10, 2017, at 1:02 PM, Tim McLaughlin <[email protected]> wrote: > > I'm checking this out now. I'm on 5.0.3 so I'll rebuild with 5.0.7 and see if we still see the issue... > > I've added: > cas.authn.ldap[0].poolPassivator=CLOSE Does this break connection pooling by presumably closing a connection when done (vs. BIND)? Tom. -- - CAS gitter chatroom: https://gitter.im/apereo/cas - CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html - CAS documentation website: https://apereo.github.io/cas - CAS project website: https://github.com/apereo/cas --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/86005518-0AC5-41E2-BC89-9D04EA672604%40ucdavis.edu. -- - CAS gitter chatroom: https://gitter.im/apereo/cas - CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html - CAS documentation website: https://apereo.github.io/cas - CAS project website: https://github.com/apereo/cas --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/46DDD207-69B1-405D-A0A8-93AD778C512B%40wwu.edu.
