cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1682) Bad configuration errors don't give much information
Date Tue, 02 Nov 2010 19:24:27 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927557#action_12927557
] 

Jonathan Ellis commented on CASSANDRA-1682:
-------------------------------------------

Can we put the stacktrace at debug?  I'm getting it beaten into me that most users really
don't like seeing stacktraces, especially if they are not java devs.

> Bad configuration errors don't give much information
> ----------------------------------------------------
>
>                 Key: CASSANDRA-1682
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1682
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.7 beta 2
>            Reporter: Gary Dusbabek
>            Assignee: Gary Dusbabek
>            Priority: Trivial
>             Fix For: 0.7.0
>
>         Attachments: v1-0001-log-a-stack-with-config-errors.txt
>
>
> When there is an error in the DatabaseDescriptor static initializer, we typically generate
an error line instead of a stack trace.  The error line is only sometimes helpful.  A stack
trace would give developers a lot more information to go on when giving support.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message