Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-12459

(7.1.0) Initializing the SyslogHandler should not do a permissions check when setting the output stream


    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.1.0.ER3
    • 7.0.7.CR2
    • None
    • None

      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.

            jperkins-rhn James Perkins
            thofman Tomas Hofman
            Jan Martiska Jan Martiska
            Jan Martiska Jan Martiska
            0 Vote for this issue
            3 Start watching this issue