Improving robustness of JBoss EAP 6.0.1 syslog logging

Issue

• JBoss server stops logging
• In JBoss EAP 6.0.1 log4j's SyslogAppender can be used to log to syslog, but it has limited recoverability from loss of connection to the backing syslogd. Syslogd downtime may occur routinely as part of log rotation. This article describes a workaround to improve robustness of syslog logging with JBoss EAP 6.0.1.
• Note: from EAP 6.2 onwards, the JBoss SyslogHandler can be used. SyslogHandler includes provisions for reconnection, and is now the recommended way to handle syslog logging: 268783 | How to use syslog in JBoss EAP 6.