You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2019/06/14 11:12:00 UTC

[jira] [Updated] (DIRSERVER-1866) When we get a OTHER error (code 80), we don't have any information about the error's origin

     [ https://issues.apache.org/jira/browse/DIRSERVER-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny updated DIRSERVER-1866:
-----------------------------------------
    Component/s: ldap

> When we get a OTHER error (code 80), we don't have any information about the error's origin
> -------------------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-1866
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1866
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>          Components: ldap
>            Reporter: Emmanuel Lecharny
>            Priority: Critical
>             Fix For: 2.0.0-RC1
>
>
> This is almost impossible to know what is the origin of the problem when we get an OTHER error (code 80). Most of the time, this is a NPE or any other error that is swallowed.
> We must not swallow the original cause, but include it into the response.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org