client.bind() never responds if server can't be reached (timeouts have no effect)

Long story short, if your server is currently down, a client.bind() never responds (meaning the callback is never called). Setting the connectTimeout and timeout on ldapjs.createClient() seem to have no effect at all here.

We first noticed this when a server went down after our app had already bound and the app then started hanging, so I’m assuming ldapjs was trying to re-bind after the connection fail[?]. I mention this because the knock on effect is that upstream client.search()s suddenly stop responding.

Reproducible like this, assuming the IP address here is valid but not responding:

> var ldapjs = require('ldapjs')
> var client = ldapjs.createClient({url:'ldap://10.146.241.10:1389', timeout:3000, connectTimeout:3000})
> client.bind(myDN, myPassword, function(err) { console.log('bind', err); });
> // ...tumbleweeds...

[maneeshmohan2000]

When the LDAP server is down and if I set the queueDisable option to false, this works fine and give me the error “{ [ConnectionError: connection unavailable] lde_message: 'connection unavailable ', lde_dn: null }”. But, this is always throwing the same error when the LDAP server is up also and if I comment out the queueDisabled option, it works. I am wondering why this is behaving like this.

[danperks]

Issue is still present now