System Alerts for LDAP errors

[GoogleCodeExporter]

What steps will reproduce the problem?
We get an email alerts every couple of days indicates:

"unable to contact ldap directory: FailOverWrapper closed while retrying 
connection"

In the logs, we see:

FATAL, servlet.TopServlet, {ebr} unable to contact ldap directory: 
FailOverWrapper closed while retrying connection

We do not know what causes this problem.
As far as we see, there is no problem with our LDAP servers (Active Directory).

What is the expected output? What do you see instead?

What version of PWM are you using?
v1.6.2 b1144 (devbuild) 

What ldap directory and version are you using?
Active Directory

Please paste any error log messages below:

Original issue reported on code.google.com by tomerazran on 6 Nov 2012 at 2:41

[GoogleCodeExporter]

Hi,

Please check:
* whether ALL of your AD's are reachable from PWM
* SSL is enabled for the AD connection and certificates are recognized 
(accepted) by PWM/Java and have not expired.
* Do you restart your AD's at a specific interval?
* Is your network misbehaving/overloaded at certain times, causing timeouts?

If that does not provide a clue of what the problem is, do post logs at trace 
level as stated in the issue template ("Please paste any error log messages 
below:")

Regards,

Menno Pieters

Original comment by menno.pi...@gmail.com on 6 Nov 2012 at 7:52

• Changed state: NeedInfo

[GoogleCodeExporter]

One other possibility worth mentioning is a firewall/router connection timeout 
between the ldap server and pwm.  Since no response from reporter, marking 
issue closed.  Please re-open with the info requested in comment #2 if your 
still having the issue.

Original comment by jrivard on 6 Dec 2012 at 8:48

• Changed state: Done

[GoogleCodeExporter]

One other possibility worth mentioning is a firewall/router connection timeout 
between the ldap server and pwm.  Since no response from reporter, marking 
issue closed.  Please re-open with the info requested in comment #1 if your 
still having the issue.

Original comment by jrivard on 6 Dec 2012 at 8:48