Re: [cas-user] LDAP timeouts after Java upgrade

2020-05-15 Thread Daniel Fisher
On Wed, May 13, 2020 at 2:43 PM Baron Fujimoto wrote: > > 2) We've empirically determined that if we shorten the default value for > the LDAP pool validation from 600s to, say, 60s > (cas.authn.ldap[0].validatePeriod=60) then this also mitigates the timeout > problem. The shortened pool

Re: [cas-user] LDAP timeouts after Java upgrade

2020-05-13 Thread Baron Fujimoto
On Wed, May 06, 2020 at 08:40:51AM -1000, Baron Fujimoto wrote: On Wed, May 06, 2020 at 02:15:39PM -0400, Daniel Fisher wrote: On Wed, May 6, 2020 at 1:40 PM Baron Fujimoto wrote: On Tue, May 05, 2020 at 11:42:01PM -0400, Daniel Fisher wrote: On Tue, May 5, 2020 at 11:15 PM Baron Fujimoto

Re: [cas-user] LDAP timeouts after Java upgrade

2020-05-07 Thread Daniel Fisher
On Wed, May 6, 2020 at 2:41 PM Baron Fujimoto wrote: > So judging by the DEBUG timestamps, only 4 ms elapses between the start of > the AuthN attempt and the SearchValidator timeout failure. Should I try to > corroborate this vis LDAP logs? > Couldn't hurt, but I wonder if there is some other

Re: [cas-user] LDAP timeouts after Java upgrade

2020-05-06 Thread Baron Fujimoto
On Wed, May 06, 2020 at 02:15:39PM -0400, Daniel Fisher wrote: On Wed, May 6, 2020 at 1:40 PM Baron Fujimoto wrote: On Tue, May 05, 2020 at 11:42:01PM -0400, Daniel Fisher wrote: >On Tue, May 5, 2020 at 11:15 PM Baron Fujimoto wrote: > >> We're running CAS 5.0.10 under Tomcat 8.5.54 with

Re: [cas-user] LDAP timeouts after Java upgrade

2020-05-06 Thread Baron Fujimoto
On Wed, May 06, 2020 at 03:48:46PM +, Ray Bon wrote: Baron, I seem to recall a bug in the JVM with some versions that affected ldap connections. It did not affect us so I really did not pay close attention. If you recently upgraded your java, you might want to look in to this. Ray My

Re: [cas-user] LDAP timeouts after Java upgrade

2020-05-06 Thread Daniel Fisher
On Wed, May 6, 2020 at 1:40 PM Baron Fujimoto wrote: > On Tue, May 05, 2020 at 11:42:01PM -0400, Daniel Fisher wrote: > >On Tue, May 5, 2020 at 11:15 PM Baron Fujimoto wrote: > > > >> We're running CAS 5.0.10 under Tomcat 8.5.54 with LDAP (389DS) for > >> authentication and attributes. We were

Re: [cas-user] LDAP timeouts after Java upgrade

2020-05-06 Thread Baron Fujimoto
On Tue, May 05, 2020 at 11:42:01PM -0400, Daniel Fisher wrote: On Tue, May 5, 2020 at 11:15 PM Baron Fujimoto wrote: We're running CAS 5.0.10 under Tomcat 8.5.54 with LDAP (389DS) for authentication and attributes. We were previously using Java 1.0.8_212 successfully. However, I recently

Re: [cas-user] LDAP timeouts after Java upgrade

2020-05-06 Thread Daniel Fisher
That JNDI bug affects Java versions 9-13. And doesn't affect CAS unless you've specifically enabled the JndiProvider. I believe the UnboundID provider is enabled by default. --Daniel Fisher On Wed, May 6, 2020 at 11:48 AM Ray Bon wrote: > Baron, > > I seem to recall a bug in the JVM with some

Re: [cas-user] LDAP timeouts after Java upgrade

2020-05-06 Thread Ray Bon
Baron, I seem to recall a bug in the JVM with some versions that affected ldap connections. It did not affect us so I really did not pay close attention. If you recently upgraded your java, you might want to look in to this. Ray On Tue, 2020-05-05 at 17:14 -1000, Baron Fujimoto wrote: Notice:

Re: [cas-user] LDAP timeouts after Java upgrade

2020-05-05 Thread Daniel Fisher
On Tue, May 5, 2020 at 11:15 PM Baron Fujimoto wrote: > We're running CAS 5.0.10 under Tomcat 8.5.54 with LDAP (389DS) for > authentication and attributes. We were previously using Java 1.0.8_212 > successfully. However, I recently upgraded the instance to use the current > version of Java