-
Bug
-
Resolution: Done
-
Major
-
7.0.7.CR2
The org.jboss.logmanager.handlers.SyslogHandler attempts to lazily connect to the syslog server. If running under a security manager and the user (deployment in WildFly's case) doesn't have control logging permissions, the write will fail. The failure is also swallowed which means there is no indication as to what the error is. Logs will just not appear on the syslog server.
- clones
-
LOGMGR-149 Initializing the SyslogHandler should not do a permissions check when setting the output stream
- Resolved
-
JBEAP-12459 (7.1.0) Initializing the SyslogHandler should not do a permissions check when setting the output stream
- Closed
- is incorporated by
-
JBEAP-10689 (7.0.z) Upgrade jboss-logmanager from 2.0.3.Final to 2.0.7.Final
- Closed