LDAP data connector timeouts

[Daniel Fisher]

On Fri, Jun 28, 2013 at 3:45 PM, Wessel, Keith <kwessel at illinois.edu> wrote:

>  Ah-ha! Like a javax.naming.CommunicationException caused by a
> java.net.ConnectException: Connection timed out, perhaps?****
>
> ** **
>
> Is this the scenario we’re talking about when a retry happens
> automatically?****
>
> **
>
Yes.

> **
>
> If so, do either of the two properties Scott mentioned provide for a
> maximum time to keep trying? I’m just fine with retries for the sake of
> getting around network hiccups as long as I can have it give up before
> mod_jk does.
>

By default it retries once and gives up. You can configure these properties
to change that behavior:

edu.vt.middleware.ldap.operationRetry - specifies the number of times an
LDAP operation will be retried if a retry exception occurs; set to -1 for
infinite retries
edu.vt.middleware.ldap.operationRetryWait - the amount of time in
milliseconds that LDAP operations should wait before retrying
edu.vt.middleware.ldap.operationRetryBackoff - factor by which to multiply
the operation retry wait time; this allows clients to progressively delay
each retry

--Daniel Fisher
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20130628/31c41d6d/attachment.html