Steven Kerdudou created LOG4J2-3518:
---------------------------------------
Summary: SocketAppender don't send headers on reconnect
Key: LOG4J2-3518
URL: https://issues.apache.org/jira/browse/LOG4J2-3518
Project: Log4j 2
Issue Type: Bug
Components: Appenders
Affects Versions: 2.16.0
Reporter: Steven Kerdudou
I found a regression on the issue
https://issues.apache.org/jira/browse/LOG4J2-181
=> when the socket is closed and we do reconnect, headers are not sent in the
new socket
There is what I found by looking in the code / Jira / git history :
The original bug was corrected by [this
commit|https://github.com/apache/logging-log4j2/commit/f91ce9347be991d052e76a4f620cc343322b4edb]
=> OutputStreamManager.java method setOutputStream
The regression was introduced by correcting this bug (Jira 2760) (with [this
commit|https://github.com/apache/logging-log4j2/commit/0c819718509e4b069fe33d30ba532d56e962ea1f])
then, when for example TcpSocketManager try to reconnect (subclass Reconnector
method connect), no header is written.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
