You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Tyler Hobbs (JIRA)" <ji...@apache.org> on 2017/02/21 22:28:44 UTC
[jira] [Commented] (CASSANDRA-13108) Uncaught exeption stack traces
not logged
[ https://issues.apache.org/jira/browse/CASSANDRA-13108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876876#comment-15876876 ]
Tyler Hobbs commented on CASSANDRA-13108:
-----------------------------------------
Pending test runs on 2.1 (skipping tests on 2.2+ since the change is quite trivial):
||branch||testall||dtest||
|[CASSANDRA-13108|https://github.com/thobbs/cassandra/tree/CASSANDRA-13108]|[testall|http://cassci.datastax.com/view/Dev/view/thobbs/job/thobbs-CASSANDRA-13108-testall]|[dtest|http://cassci.datastax.com/view/Dev/view/thobbs/job/thobbs-CASSANDRA-13108-dtest]|
> Uncaught exeption stack traces not logged
> -----------------------------------------
>
> Key: CASSANDRA-13108
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13108
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Christopher Batey
> Assignee: Christopher Batey
> Priority: Trivial
>
> In a refactoring to parameterized logging we lost the stack traces of uncaught exceptions. This means, apart from the thread, I have no idea where they come from e.g.
> {code}
> ERROR [OptionalTasks:1] 2017-01-06 12:53:14,204 CassandraDaemon.java:231 - Exception in thread Thread[OptionalTasks:1,5,main]
> java.lang.NullPointerException: null
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)