LDAP data connector timeouts

[Wessel, Keith]

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?

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.

Keith


From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Daniel Fisher
Sent: Friday, June 28, 2013 2:38 PM
To: Shib Users
Subject: Re: LDAP data connector timeouts

On Fri, Jun 28, 2013 at 3:01 PM, Wessel, Keith <kwessel at illinois.edu<mailto:kwessel at illinois.edu>> wrote:
That would make sense, but there's a confusing statement in the VT LDAP java lib documentation under the design goals:
3.  Automatic connection handling. Timed out connections automatically retry and TLS/SSL
is negotiated transparently.

Any idea what "Timed out connections automatically retry" means?

It means if connections are dropped by the server (or load balancer) the library will attempt to reconnect and perform the operation again.
More specifically, the operation must produce a CommunicationException or ServiceUnavailableException to invoke this behavior.

--Daniel Fisher

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20130628/72d2973a/attachment.html