[jira] [Commented] (IGNITE-1433) .Net: Add IgniteException.JavaStackTrace

["Pavel Tupitsyn (JIRA)" <ji...@apache.org>]

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

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

1) It does help A LOT, almost every day I face a situation where I have to run tests with console open to find out what's going on. It is a waste of time, and it is not always easy to find related exception in the console. 
We cannot predict every single situation to improve usability with it.

2) This makes sense. Instead of IgniteException.JavaStackTrace, we can populate InnerException property with some JavaException instance, or even plain Exception with java trace in the message. This way we don't pollute the API. Thoughts?

I still think that this ticket is very important and will defend it as long as I can :)



> .Net: Add IgniteException.JavaStackTrace
> ----------------------------------------
>
>                 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: 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)