Hi On 03/09/2016 06:33 AM, Abhinandan Prateek wrote: > In 4.5 there is a timeout param that was added ‘ldap.read.timeout’ that > defaults to 1000, > It should be set to about 6000 and that should resolve the read timeout > that you guys see.
we already set it to 6000 (and more) as you can see here: 2016-02-29 10:05:42,382 DEBUG [cloudstack.ldap.LdapManagerImpl] (catalina-exec-4:ctx-9ffa7c60) ldap Exception: javax.naming.NamingException: LDAP response read timed out, timeout used:6000ms.; remaining name 'dc=foo,dc=bar' The only thing that "solved" the problem was -Dcom.sun.jndi.ldap.connect.pool.timeout=60000 We have a suspicion that the issue is related somehow in our ldap setup (tcp, or openldap config) in relation to the connection pooling in cloudstack. René
