Configuration of vt-ldap within DataConnector

[Daniel Fisher]

On Fri, Sep 9, 2011 at 4:01 PM, Yuji Shinozaki <ys2n at virginia.edu> wrote:

> I am spinning off a different thread about the configuration of the vt-ldap
> implementation of the ldap dataconnector to keep the noise down on the
> original thread.
>
> Daniel,
>
> How are the exceptions that are caught by the vt-ldap library specified in
> the configs?  The vt-ldap docs (
> http://code.google.com/p/vt-middleware/wiki/vtldapProperties#Properties)
> show them as being specified like so:
>
> {CommunicationException, ServiceUnavailableException}
>
> So, I am assuming that it assumes javax.naming.* classes.   Can you specify
> exception classes in other packages?


You can specify any NamingException.


>  Also, is it simply an instanceof operation and can you specify and match
> on superclasses or interfaces?
>

NamingException.isInstance(..)


>
> Admittedly, these last two questions are academic, because I just need to
> retry on javax.naming.TimeLimitExceededException, so I am presuming I just
> need to specify it thusly:
>
> <LDAPProperty name="edu.vt.middleware.ldap.operationRetryExceptions"
> value="{CommunicationException, ServiceUnavailableException,
> TimeLimitExceededException}" />
>
>
 <LDAPProperty name="edu.vt.middleware.ldap.operationRetryExceptions"
value="javax.naming.CommunicationException,javax.naming.ServiceUnavailableException,javax.naming.TimeLimitExceededException"
/>

Are you sure this is what you want? An operation retry closes and reopens
the connection, then presumably you'd get the same
TimeLimitExceededException again. Note that LimitExceededException is
ignored by the search result handler. So even if it occurs, you'll still get
any results that were retrieved before the exception.

--Daniel Fisher
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20110909/77906bde/attachment.html