You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Markus Weimer (JIRA)" <ji...@apache.org> on 2016/09/28 20:45:20 UTC

[jira] [Resolved] (REEF-1618) Add stack trace to exceptions handled in TaskHostBase

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

Markus Weimer resolved REEF-1618.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 0.16

Resolved via [#1138|https://github.com/apache/reef/pull/1138]

> Add stack trace to exceptions handled in TaskHostBase
> -----------------------------------------------------
>
>                 Key: REEF-1618
>                 URL: https://issues.apache.org/jira/browse/REEF-1618
>             Project: REEF
>          Issue Type: Improvement
>          Components: IMRU, REEF.NET
>            Reporter: Mariia Mykhailova
>            Assignee: Mariia Mykhailova
>            Priority: Minor
>              Labels: FT
>             Fix For: 0.16
>
>
> When user code throws exception, {{TaskHostBase.HandleException}} logs some information about it, but not all, for example, stack trace is missing. On the driver side, we also don't get stack trace. This is extremely inconvenient when troubleshooting an exception, we need to log stack trace at some point. 
> As a fix, I suggest that we log full information about {{originalException}} in {{TaskHostBase.HandleException}} before passing on new exception.



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