[
https://issues.apache.org/jira/browse/IGNITE-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381943#comment-15381943
]
Pavel Tupitsyn edited comment on IGNITE-1433 at 7/18/16 9:09 AM:
-----------------------------------------------------------------
* JavaStackTrace property removed.
* JavaException class added and used as InnerException.
Result:
* Exceptions look exactly the same as before
* InnerException contains complete Java stack trace, so the user can dig into
it and find the root cause
* Exception.ToString() shows complete exception hierarchy, so the user will see
InnerException details when running from console. This solves the issue with
Spring and other startup failures.
was (Author: ptupitsyn):
* JavaStackTrace property removed.
* JavaException class added and used as InnerException.
Result:
* Exceptions look exactly the same as before
* InnerException contains complete Java stack trace, so the user can dig into
it and find the root cause
* Exception.ToString() shows complete exception hierarchy, so the user will see
InnerException details when running from console.
> .NET: Add Java stack trace to IgniteException
> ---------------------------------------------
>
> Key: IGNITE-1433
> URL: https://issues.apache.org/jira/browse/IGNITE-1433
> Project: Ignite
> Issue Type: Task
> Components: platforms
> Affects Versions: 1.1.4
> Reporter: Vladimir Ozerov
> Assignee: Vladimir Ozerov
> Labels: .net
> Fix For: 1.7
>
>
> 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)
