ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Tupitsyn (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-1433) .Net: Add IgniteException.JavaStackTrace
Date Wed, 09 Dec 2015 16:03:11 GMT

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

Pavel Tupitsyn commented on IGNITE-1433:
----------------------------------------

* JavaStackTrace removed from some things like ClusterTopologyException
* NPE and other Java exceptions without .NET mapping: we convert these to IgniteException,
so the stack trace is preserved. Double-checked this with actual recent NPE in Services tests
* Bad classpath (class or method not found): message contains all required information (class/method
name), no need for stack trace.

> .Net: Add IgniteException.JavaStackTrace
> ----------------------------------------
>
>                 Key: IGNITE-1433
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1433
>             Project: Ignite
>          Issue Type: Task
>          Components: interop
>    Affects Versions: 1.1.4
>            Reporter: Vladimir Ozerov
>            Assignee: Pavel Tupitsyn
>             Fix For: 1.6
>
>
> Propagate java stack trace as a string in ExceptionUtils.GetException and write it to
a new field in IgniteException class.
> This will simplify debugging for us both locally and when getting error reports from
clients.



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

Mime
View raw message