Add unboundid configurable option RetryFailedOperationsDueToInvalidConnections
Some ldap servers and/or network appliances between Sakai and the ldap server may shutdown idle connections and the unboundid sdk will throw an exception
several unboundid forums suggest using:
from the first article above:
if an operation performed directly against the pool (i.e., using one of the pool's add, bind, search, etc. methods, rather than checking a connection out and doing something with it) does not complete successfully, then the default health check will determine whether that failure may indicate that the connection is no longer valid. If the health check indicates that the connection may no longer be valid, then it will throw away that connection and create another one to take its place. If automatic retry is enabled, then the pool will automatically retry that failed operation on the newly-established connection.
It would be great to add a configurable option in unboundid-ldap.xml to allow setting setRetryFailedOperationsDueToInvalidConnections
note that there are two overloaded versions of that function:
It would be simplest to use the boolean version, but the other would give more fine tuned options.