You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Nate McCall (Created) (JIRA)" <ji...@apache.org> on 2011/11/22 22:54:40 UTC
[jira] [Created] (CASSANDRA-3525) Uncaught exceptions in CLI can
produce obtuse "null" error message
Uncaught exceptions in CLI can produce obtuse "null" error message
------------------------------------------------------------------
Key: CASSANDRA-3525
URL: https://issues.apache.org/jira/browse/CASSANDRA-3525
Project: Cassandra
Issue Type: Bug
Components: Tools
Affects Versions: 1.0.3
Reporter: Nate McCall
Assignee: Nate McCall
Priority: Minor
CliMain#processStatementInteractive method relies on the getMessage method of Exception. This method can return null per JavaDocs on Exception hierarchy.
Checking for null and dumping the exception class would be more useful, particularly to new users reporting problems.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-3525) Uncaught exceptions in CLI can
produce obtuse "null" error message
Posted by "Nate McCall (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nate McCall updated CASSANDRA-3525:
-----------------------------------
Attachment: 3525.txt
Adds the exception class name if no other meaningful information is available regarding the error.
> Uncaught exceptions in CLI can produce obtuse "null" error message
> ------------------------------------------------------------------
>
> Key: CASSANDRA-3525
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3525
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Affects Versions: 1.0.3
> Reporter: Nate McCall
> Assignee: Nate McCall
> Priority: Minor
> Attachments: 3525.txt
>
>
> CliMain#processStatementInteractive method relies on the getMessage method of Exception. This method can return null per JavaDocs on Exception hierarchy.
> Checking for null and dumping the exception class would be more useful, particularly to new users reporting problems.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CASSANDRA-3525) Uncaught exceptions in CLI can
produce obtuse "null" error message
Posted by "Jonathan Ellis (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-3525.
---------------------------------------
Resolution: Duplicate
fixed in CASSANDRA-3508
> Uncaught exceptions in CLI can produce obtuse "null" error message
> ------------------------------------------------------------------
>
> Key: CASSANDRA-3525
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3525
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Affects Versions: 1.0.3
> Reporter: Nate McCall
> Assignee: Nate McCall
> Priority: Minor
> Attachments: 3525.txt
>
>
> CliMain#processStatementInteractive method relies on the getMessage method of Exception. This method can return null per JavaDocs on Exception hierarchy.
> Checking for null and dumping the exception class would be more useful, particularly to new users reporting problems.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira