ldap timeout and/or recycle stale connections

Overnight my ejabberd instance seems to collect stale ldap connections.

I am using ldap auth, ldap shared roster, and ldap vcards.

I have two ldap servers configured and on start I show 24 connections to my ldap servers (total; 12 on each)

over night these connections grow stale or otherwise problematic- when I attempt to login in the morning nothing works. I will either have a very long delay for auth followed by no roster, or a prompt for my login credentials.

Is there a timeout or setting I can use for ldap to recycle these connections on a regular basis?

Syndicate content