[jira] [Commented] (IGNITE-12797) Add command line option to CommandHandler to be able to see full stack trace and cause exception in log in case of error.
[ https://issues.apache.org/jira/browse/IGNITE-12797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074285#comment-17074285 ] Kirill Tkalenko commented on IGNITE-12797: -- [~ivan.glukos] I resolved merge conflict and got a visa ^ > 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)
[jira] [Commented] (IGNITE-12797) Add command line option to CommandHandler to be able to see full stack trace and cause exception in log in case of error.
[ https://issues.apache.org/jira/browse/IGNITE-12797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074284#comment-17074284 ] Ignite TC Bot commented on IGNITE-12797: {panel:title=Branch: [pull/7544/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel} [TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=5185097&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)
[jira] [Commented] (IGNITE-12797) Add command line option to CommandHandler to be able to see full stack trace and cause exception in log in case of error.
[ https://issues.apache.org/jira/browse/IGNITE-12797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073988#comment-17073988 ] Ivan Rakov commented on IGNITE-12797: - [~ktkale...@gridgain.com] Please get green TC visa and resolve merge conflicts. > 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)
[jira] [Commented] (IGNITE-12797) Add command line option to CommandHandler to be able to see full stack trace and cause exception in log in case of error.
[ https://issues.apache.org/jira/browse/IGNITE-12797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17067010#comment-17067010 ] Kirill Tkalenko commented on IGNITE-12797: -- [~akalashnikov] Please merge. > 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)
[jira] [Commented] (IGNITE-12797) Add command line option to CommandHandler to be able to see full stack trace and cause exception in log in case of error.
[ https://issues.apache.org/jira/browse/IGNITE-12797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17067006#comment-17067006 ] 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 Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=5157041]] {panel} [TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=5155031&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)
[jira] [Commented] (IGNITE-12797) Add command line option to CommandHandler to be able to see full stack trace and cause exception in log in case of error.
[ 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)
[jira] [Commented] (IGNITE-12797) Add command line option to CommandHandler to be able to see full stack trace and cause exception in log in case of error.
[ https://issues.apache.org/jira/browse/IGNITE-12797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17062350#comment-17062350 ] Kirill Tkalenko commented on IGNITE-12797: -- [~ilyak] Can you give me an example? > 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)
[jira] [Commented] (IGNITE-12797) Add command line option to CommandHandler to be able to see full stack trace and cause exception in log in case of error.
[ https://issues.apache.org/jira/browse/IGNITE-12797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061628#comment-17061628 ] Ilya Kasnacheev commented on IGNITE-12797: -- Can we have a positive test, one where the presence of this option does not prevent successful operation from succeeding? > 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)
[jira] [Commented] (IGNITE-12797) Add command line option to CommandHandler to be able to see full stack trace and cause exception in log in case of error.
[ https://issues.apache.org/jira/browse/IGNITE-12797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061452#comment-17061452 ] Kirill Tkalenko commented on IGNITE-12797: -- ^ Falls often, not through my fault. > 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)
[jira] [Commented] (IGNITE-12797) Add command line option to CommandHandler to be able to see full stack trace and cause exception in log in case of error.
[ https://issues.apache.org/jira/browse/IGNITE-12797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061454#comment-17061454 ] Kirill Tkalenko commented on IGNITE-12797: -- [~akalashnikov] Please merge. > 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)
[jira] [Commented] (IGNITE-12797) Add command line option to CommandHandler to be able to see full stack trace and cause exception in log in case of error.
[ 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)