[rabbitmq-discuss] LDAP backend problem

Simon MacMullen simon at rabbitmq.com
Wed Feb 19 10:49:46 GMT 2014

On 19/02/14 08:55, Kristian Jensen wrote:
> Why is the LDAP module not robust againt unavailable LDAP backens? -
> could you intruduce a sort of healtcheck?

We just pass the list of servers down to the underlying Erlang LDAP 
implementation (eldap). As far as I can see that then attempts to 
establish a TCP connection to each server in turn; on failure it tries 
the next one.

I assume that attempting to connect to one of your unavailable LDAP 
servers is taking a long time (i.e. connections are timing out rather 
than coming back with "connection refused" or "no route to host" or 

One thing I notice is that eldap supports the idea of a connection 
timeout (defaulting to infinity); we don't support changing that from 
the default. I'll file a bug to fix that.

But if LDAP connections are timing out then we are going to struggle to 
handle that without incurring similar delays in AMQP / HTTP / STOMP / 

Cheers, Simon

Simon MacMullen
RabbitMQ, Pivotal

More information about the rabbitmq-discuss mailing list