[
https://issues.apache.org/jira/browse/IGNITE-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046970#comment-15046970
]
Pavel Tupitsyn commented on IGNITE-1433:
----------------------------------------
1) Agreed, but it is as unsafe as it was before
2) Agreed
3) In such cases I add Java stack trace to the message.
However, simply logging in Java is a bad usability option:
* Looking in Java log is inconvenient, in contrary to seeing all the details in
debugger immediately
* Exceptions in Java log have to be matched to particular exceptions in .NET
* User may be sending exceptions over network or storing them, Java log won't
be included
* Users are not aware of a Java log, we'll often have to ask them explicitly to
include it during investigation
There is a range of issues when we absolutely need Java stack trace on .NET
side, such as startup failures, topology join failures and manager startup
failures.
Let's address these initialization issues first.
> .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)
