directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kiran Ayyagari (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRSERVER-1866) When we get a OTHER error (code 80), we don't have any information about the error's origin
Date Thu, 20 Feb 2014 11:54:21 GMT

    [ https://issues.apache.org/jira/browse/DIRSERVER-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906889#comment-13906889
] 

Kiran Ayyagari commented on DIRSERVER-1866:
-------------------------------------------

Think this was already taken care of, no? Emmanuel?

> 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
>            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
(v6.1.5#6160)

Mime
View raw message