[
https://issues.apache.org/jira/browse/LOG4J2-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16776535#comment-16776535
]
Ralph Goers commented on LOG4J2-2554:
-------------------------------------
Can you provide a test that exhibits this behavior? In looking at the code I
don't see any difference between the TLS and TCP appenders related to buffering
or flushing. In fact, the TLS appender delegates all writing to the TCP syslog
appender.
> TLS syslog: events are not dispatched until client terminates
> -------------------------------------------------------------
>
> Key: LOG4J2-2554
> URL: https://issues.apache.org/jira/browse/LOG4J2-2554
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Reporter: a b
> Priority: Major
>
> Hi.
> I am testing syslog dispatch through log4j2.
> server: syslog-ng 3.6.5 (ubuntu, client authentication disabled)
> client: configured 3 appenders: udp, tcp and tls (xml file, monitored every 2
> sec)
> When sending using udp and tcp appenders, messages are received promptly at
> the server side.
> when sending using tls appender, I can see:
> # a connection established on the server side.
> # events are generated on the client side
> # No events are captured on server.
> Upon terminating the client, events are captured on the server side. So it
> seems events are queued on the client, and are not flushed until the client
> terminates. This happens regardless of me setting 'immediateFlush'
> bufferedIO' or 'bufferSize'.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
