[
https://issues.apache.org/jira/browse/LOG4J2-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16128998#comment-16128998
]
ASF GitHub Bot commented on LOG4J2-2013:
----------------------------------------
Github user taylorp36 commented on the issue:
https://github.com/apache/logging-log4j2/pull/108
The code path is very similar; the tests in
**org.apache.logging.log4j.core.appender.net** call the appender directly, and
the test in **org.apache.logging.log4j.core.appender** applies the appender to
the Logger, and uses the logger to send the event (via the appender). I don't
think there is much benefit with both if we just want to test that the secure
appender can send events. Would you like me to remove the test I added in
SocketAppenderTest? Any suggestions about the initial design of the fix?
> SslSocketManager does not apply SSLContext on TCP reconnect
> -----------------------------------------------------------
>
> Key: LOG4J2-2013
> URL: https://issues.apache.org/jira/browse/LOG4J2-2013
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.8.2
> Reporter: Taylor Patton
> Assignee: Gary Gregory
> Fix For: 2.9
>
>
> The SslSocketManger is not applying the SSLContext correctly when the TCP
> connection is restarted. Currently the SslSocketManager inherits a
> Reconnector class from TcpSocketManger, which only restarts the TCP
> connection and does not apply SSL correctly.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
