David Mollitor created NIFI-8083:
------------------------------------
Summary: 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
{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)