directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <>
Subject [jira] [Reopened] (DIRAPI-206) BindRequest logs exception on valid call to setter
Date Sat, 01 Nov 2014 10:18:33 GMT


Emmanuel Lecharny reopened DIRAPI-206:

Reopeing the issue. The proposed solution is theorically right, but from a pragmatic POV,
it's a bit blind.

The best solution, as Kiran suggest, is to switch the LOG to debug for this case.

> BindRequest logs exception on valid call to setter
> --------------------------------------------------
>                 Key: DIRAPI-206
>                 URL:
>             Project: Directory Client API
>          Issue Type: Bug
>    Affects Versions: 1.0.0-M24
>            Reporter: Peter Becker
> We are using DIRAPI to connect to our corporate ActiveDirectory and it seems impossible
to do so without getting an exception logged in our application log, even on successful operations.
This is a concern since the exception creates noise potentially hiding real issues.
> The problem is described in
but the resolution is not sufficient for our purposes.
> The issue is caused by this bit of code in BindRequestImpl:
> {code}
>     public BindRequest setName( String name )
>     {
> = name;
>         try
>         {
>             this.dn = new Dn( name );
>         }
>         catch ( LdapInvalidDnException e )
>         {
>             // This might still be a valid DN (Windows AD binding for instance)
>    "Unable to convert the name to a DN.", e );
>             this.dn = null;
>         }
>         return this;
>     }
> {code}
> The comment even indicates that the call might be perfectly valid. I think it would be
much better to either drop the exception completely, or -- if it is required in other scenarios
-- to skip the attempt of creating the DN field completely if some flag is set (extra parameter
/ field / subclass). Since the name field is private it can not be done from the client side.
> This is a potential showstopper for us -- we do not like telling our support staff to
ignore exceptions in logs.

This message was sent by Atlassian JIRA

View raw message