You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "mck (JIRA)" <ji...@apache.org> on 2019/02/25 23:52:00 UTC
[jira] [Commented] (CASSANDRA-14528) Provide stacktraces for
various error logs
[ https://issues.apache.org/jira/browse/CASSANDRA-14528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777411#comment-16777411 ]
mck commented on CASSANDRA-14528:
---------------------------------
{quote}So as soon as there's one format argument, then any tailing exception will also be interpreted as a format argument, and we get exception.toString().{quote}
To further clarify… while SLF4J proposes to accept the final argument in the vararg as a throwable, and if so print it as a stack-trace. The LogBack implementation of the SLF4J Logger does not do this.
> Provide stacktraces for various error logs
> ------------------------------------------
>
> Key: CASSANDRA-14528
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14528
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/Core
> Reporter: Stefan Podkowinski
> Assignee: Stefan Podkowinski
> Priority: Major
> Fix For: 4.0
>
>
> We should reintroduce some stack traces that have gone missing since CASSANDRA-13723 (ba87ab4e954ad2). The cleanest way would probably to use {{String.format}} for any custom messages, e.g. {{logger.error(String.format("Error using param {}", param), e)}}, so we make this more implicit and robust for coming api changes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org