[
https://issues.apache.org/jira/browse/OAK-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16346825#comment-16346825
]
Chetan Mehrotra edited comment on OAK-7226 at 1/31/18 1:33 PM:
---------------------------------------------------------------
Logback also supports it [1]. Also this is stated in
[Logger|https://www.slf4j.org/api/org/slf4j/Logger.html] docs
bq. Note that logging statements can be parameterized in presence of an
exception/throwable.
[1]
https://github.com/qos-ch/logback/blob/master/logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggingEvent.java#L114
was (Author: chetanm):
Logback also supports it [1]
[1]
https://github.com/qos-ch/logback/blob/master/logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggingEvent.java#L114
> Warn messages ignoring exception parameter
> ------------------------------------------
>
> Key: OAK-7226
> URL: https://issues.apache.org/jira/browse/OAK-7226
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: blob-plugins
> Affects Versions: 1.8.0
> Reporter: Marcel Reutegger
> Priority: Minor
> Fix For: 1.10
>
>
> There are a few usages of Logger.warn() with a pattern similar to this
> example:
> {noformat}
> log.warn("Error occurred while fetching DataRecord for identifier {}", input,
> exeption);
> {noformat}
> The intention probably is that the third parameter is treated as an exception
> and e.g. logged with the stack trace. However, this method signature
> interprets the exception as a second argument for the message format. This
> means the exception is effectively ignored.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
