[
https://issues.apache.org/jira/browse/IGNITE-12797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061451#comment-17061451
]
Ignite TC Bot commented on IGNITE-12797:
----------------------------------------
{panel:title=Branch: [pull/7544/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS (Indexing){color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5136298]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5135608&buildTypeId=IgniteTests24Java8_RunAll]
> Add command line option to CommandHandler to be able to see full stack trace
> and cause exception in log in case of error.
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-12797
> URL: https://issues.apache.org/jira/browse/IGNITE-12797
> Project: Ignite
> Issue Type: Improvement
> Reporter: Kirill Tkalenko
> Assignee: Kirill Tkalenko
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In case of error control.sh can print common error message without any
> information about root cause of error. Printing full stack trace and cause
> can ease the analysis. User should be able to turn it on when launching
> control.sh with specific option.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
