SSLSocketChannel Logging Improvement

         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.