We have a system currently running 4.7.0 which is connected to an Active-Directory thru LDAP and we had no issues so far. it got upgraded from: 4.2.1 to 4.6.0 to 4.7.0
Ilya, does your issues could be related to LDAP changes required from an upgrade: http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4.4/upgrade/upgrade_notes.html#active-directory-authentication-ldap PL On Wed, Mar 9, 2016 at 4:45 AM, Rene Moser <m...@renemoser.net> wrote: > 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é > > >
