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

[jira] [Updated] (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 ]

Mariia Mykhailova updated REEF-1618:
------------------------------------
    Labels: FT  (was: )

> 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
>
> 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)