cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-13108) Uncaught exeption stack traces not logged
Date Wed, 22 Feb 2017 16:21:44 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-13108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tyler Hobbs updated CASSANDRA-13108:
------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.11.0
                   3.0.12
                   2.2.10
                   2.1.18
           Status: Resolved  (was: Testing)

Test results look good, so I've committed this to 2.1 as {{3c2f87610de0f11071f3d5c005c1d14c06c832f8}}
and merged up to 2.2, 3.0, 3.11, and trunk.  Thanks for the 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
>             Fix For: 2.1.18, 2.2.10, 3.0.12, 3.11.0
>
>
> 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)

Mime
View raw message