You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2017/05/03 13:48:04 UTC

[jira] [Resolved] (IGNITE-5135) .NET: Improve remote error propagation

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

Pavel Tupitsyn resolved IGNITE-5135.
------------------------------------
    Resolution: Fixed

> .NET: Improve remote error propagation
> --------------------------------------
>
>                 Key: IGNITE-5135
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5135
>             Project: Ignite
>          Issue Type: Improvement
>          Components: platforms
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Minor
>             Fix For: 2.1
>
>
> When we rethrow remote exceptions, we should wrap them in another exception to preserve remote stack traces.
> For example, {{ComputeAbstractClosureTask.OnResult}} uses {{throw err}}, where {{err}} is a deserialized remote exception. This call causes remote stack trace loss.
> Instead we should do {{throw new IgniteException("Remote computation failed", err)}} which will preserve remote stack trace.
> Same should be done for other remote invocation scenarios (event listeners and so on).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)