[ https://issues.apache.org/jira/browse/IGNITE-12797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17062375#comment-17062375 ]
Ilya Kasnacheev commented on IGNITE-12797: ------------------------------------------ Something akin to {code} ./control.sh --print-err-stack-trace --status {code} Also a non-parameter error should be checked, such as {code} ./control.sh --print-err-stack-trace --host unresponsive-host --status {code} > 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)