Hi, Thanks for your help, it was just for testing 20000 (20s) in fact i use 2000 (2s) I remove the 2nd ldap host and it don't work anymore : cas is unavailable Matthieu
----- Mail original ----- De: "Marvin Addison" <[email protected]> À: [email protected] Envoyé: Mercredi 5 Janvier 2011 17:02:04 Objet: Re: [cas-user] CAS LDAP time exceeded > <entry> > <key> > <value>com.sun.jndi.ldap.read.timeout</value> > </key> <value>20000</value> 20 seconds is an eternity to wait for results to be available, which I believe is the root cause of TimeLimitExceeded. One thing I noted is that it looks like you have an error in your deployerConfigContext.xml: > <property name="urls"> > <list> > <value>${ldap.host.1}</value> > <value>ldaps://ldap2.rutgers.edu/</value> > </list> Surely you're not hitting a Rutgers directory from France. I wonder if that's the cause, since it seems plausible that in the concurrent authentication case, the second (invalid) host would be contacted since the primary is busy and it would time out. I honestly don't remember the logic of how JNDI does pooling, whether it's round-robin or least-active, but it's probably round robin which casts doubt on my hypothesis. Let's correct the config in any case since it clearly appears wrong and see what happens. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
