[
https://issues.apache.org/jira/browse/NIFI-8083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17247957#comment-17247957
]
ASF subversion and git services commented on NIFI-8083:
-------------------------------------------------------
Commit 8eb0db6b38173b3993c8e10babd42284ee42f35b in nifi's branch
refs/heads/main from David Mollitor
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=8eb0db6 ]
NIFI-8083: SSLSocketChannel Logging Improvement
Fixed additional logs messages with same issue
Signed-off-by: Matthew Burgess <[email protected]>
This closes #4722
> SSLSocketChannel Logging Improvement
> ------------------------------------
>
> Key: NIFI-8083
> URL: https://issues.apache.org/jira/browse/NIFI-8083
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Security
> Reporter: David Mollitor
> Priority: Trivial
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {code:java}
> logger.error("{} Failed to connect due to {}", this, e);
> if (logger.isDebugEnabled()) {
> logger.error("", e);
> }
> {code}
> I just came across this in troubleshooting an issue. The "e" Exception is
> displayed in the logging with the full stack trace, which was helpful, but it
> was not passed to the second anchor "{}" and the literal anchor showed up in
> the message. I think that as long as SLF4J sees an Exception as the last
> parameter it will print the stack trace, regardless of the anchor.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
