Uploaded image for project: 'Apache NiFi'
  1. Apache NiFi
  2. NIFI-8083

SSLSocketChannel Logging Improvement

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Trivial
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.13.0
    • Component/s: Security
    • Labels:
      None

      Description

               logger.error("{} Failed to connect due to {}", this, e);
                  if (logger.isDebugEnabled()) {
                      logger.error("", e);
                  }
      

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                belugabehr David Mollitor
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 0.5h
                  0.5h