[jboss-jira] [JBoss JIRA] (WFLY-6243) TCP Syslog handler cannot log some messages after reconnect

[Ondrej Lukas (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-6243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondrej Lukas updated WFLY-6243:
-------------------------------
    Attachment: logging-deployment.war


> TCP Syslog handler cannot log some messages after reconnect
> -----------------------------------------------------------
>
>                 Key: WFLY-6243
>                 URL: https://issues.jboss.org/browse/WFLY-6243
>             Project: WildFly
>          Issue Type: Bug
>          Components: Logging
>            Reporter: Ondrej Lukas
>            Assignee: James Perkins
>         Attachments: logging-deployment.war
>
>
> In case when logging to syslog through TCP protocol is configured and syslog port becomes unreachable then after syslog restart some messages can be thrown away. 
> It seems syslog handler needs to another two logs for correct closing original TCP connection. In case when syslog is restarted and
> * no message is logged during syslog is unreachable then the first two messages will not be logged to syslog after syslog is running again
> * one message is attempted to be logged during syslog is unreachable then the first message will not be logged to syslog after syslog is running again
> * two and more messages are attempted to be logged during syslog is unreachable then everything is logged correctly after syslog is running again



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)