[ https://issues.apache.org/jira/browse/CASSANDRA-13108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher Batey updated CASSANDRA-13108: ------------------------------------------ Status: Patch Available (was: Open) Trivial patch here: https://github.com/chbatey/cassandra-1/commit/fc81ff82fc96288336836d066d249b35edf44994.patch > 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.4#6332)