[ https://issues.jboss.org/browse/WFCORE-1401?page=com.atlassian.jira.plugi... ] James Perkins closed WFCORE-1401. --------------------------------- Resolution: Rejected This is the expected behavior. Here's what happens in the {{org.jboss.logmanager.handlers.SyslogHandler}}. * First message when the server is down is sent and no error is raised by the {{java.net.Socket}} therefore the syslog handler thinks all is okay * A second message is sent this time the {{java.net.Socket}} throws a {{java.net.SocketException: Broken pipe}}. The syslog handler reports this and the socket attempts to reconnect, but the message is not sent again. * The third message succeeds because the connection has once again been resestablished This works in your second scenario as well because the socket keeps attempting to connect. A successful connection is made by the time you send your third message. There is a possibility the message might not be sent until the fourth or fifth message even. It all depends on when the socket is reconnected. That said there is a setting, {{blockOnReconnect}} which defaults to {{false}}, that will guarantee the third message is logged. The handler will block until a connection has been reestablished. I would however only suggest this be used wrapped in an {{async-handler}} as you could stall the entire server until the connection has been reestablished. -- This message was sent by Atlassian JIRA (v6.4.11#64026)