[
https://issues.apache.org/jira/browse/LOG4J2-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16127740#comment-16127740
]
ASF GitHub Bot commented on LOG4J2-2013:
----------------------------------------
GitHub user taylorp36 opened a pull request:
https://github.com/apache/logging-log4j2/pull/108
LOG4J2-2013 Handle reconnect in SSLSocketManager without losing SSLCo…
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/taylorp36/logging-log4j2 master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/logging-log4j2/pull/108.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #108
----
commit f53c9b0de944f171c4777ea342e3944aeeecaf8b
Author: Taylor Patton <[email protected]>
Date: 2017-08-14T20:57:13Z
LOG4J2-2013 Handle reconnect in SSLSocketManager without losing SSLContext
----
> 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
> 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)
