[
https://issues.jboss.org/browse/WFCORE-1369?page=com.atlassian.jira.plugi...
]
James Perkins commented on WFCORE-1369:
---------------------------------------
Note the PR allows for a better reconnect, but the reconnect will not work as expected in
the description of this issue. If a syslog server goes down or the connection is dropped
it will take 2 messages sent before a third one will be logged. On the first message sent
after a disruption will simply be ignored by the {{java.net.Socket}}. The second message
sent will throw a {{java.net.SocketException: Broken pipe}}. This error is thrown by the
syslog audit log handler and the connection state is reset indicating it should be
reconnected. Finally the third message will go through.
Audit logging to TCP syslog is stopped after syslog restart
-----------------------------------------------------------
Key: WFCORE-1369
URL:
https://issues.jboss.org/browse/WFCORE-1369
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 2.0.10.Final
Reporter: Ondrej Lukas
Assignee: James Perkins
In case when audit logging to TCP syslog is enabled and syslog server is restarted then
audit logging to syslog is stopped. UDP works correctly. It can be related to issue [1].
[1]
https://issues.jboss.org/browse/LOGMGR-123
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)