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

Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org> on 2016/03/31 21:02:25 UTC

[jira] [Updated] (UIMA-4660) Improve DUCC JP connection error handling

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

Jerry Cwiklik updated UIMA-4660:
--------------------------------
    Fix Version/s:     (was: 2.0.2-Ducc)

> Improve DUCC JP connection error handling
> -----------------------------------------
>
>                 Key: UIMA-4660
>                 URL: https://issues.apache.org/jira/browse/UIMA-4660
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>    Affects Versions: 2.0.1-Ducc
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.1.0-Ducc
>
>
> When JP looses connection to its JD, it logs a stack trace each time.To users the stack trace and a message are not clear enough to determine what happen. 
> Instead of logging a stack trace, log a more meaningful message like :
> Failed N times to connect the JD .. it may have failed 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)