[jira] [Closed] (LOG4J2-2554) TLS syslog: events are not dispatched until client terminates

["a b (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4J2-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

a b closed LOG4J2-2554.
-----------------------
    Resolution: Not A Problem

root cause appears to-be on server-side.

> 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)