[logback-dev] [JIRA] Created: (LBCLASSIC-327) SyslogAppender doesn't respect %nopex, outputs stack trace

[Don Faulkner (JIRA)]

SyslogAppender doesn't respect %nopex, outputs stack trace
----------------------------------------------------------

                 Key: LBCLASSIC-327
                 URL: http://jira.qos.ch/browse/LBCLASSIC-327
             Project: logback-classic
          Issue Type: Bug
          Components: appender, layout
    Affects Versions: 1.0.0
         Environment: Ubuntu (11.10)  & Red Hat (RHEL 5.8) Linux, Java 1.6, Shibboleth Identity Provider 2.3.6
            Reporter: Don Faulkner
            Assignee: Logback dev list


(See http://mailman.qos.ch/pipermail/logback-user/2012-April/003096.html)

When using SyslogAppender, stack trace output appears in the output of the Appender, contrary to the configured (or programmed) layout.

When my SyslogAppender is used, stack traces appear in my syslog output, even though I don't want them. I've included a "%nopex" at the end of the SuffixPattern value, but this has not stopped the stack traces from appearing. I've tested a matching RollingFileAppender, where "%nopex" has the expected behavior.

I'd expect that SyslogAppender would omit stack traces by default, or at least give me a way to omit them.

I've looked at the source for SyslogAppender.java, and I see (about line 43) that the prefixPattern already includes "%nopex" so I'm at a loss as to why I'm seeing stack traces to begin with.

I've configured a SyslogAppender as follows. 
The "%nopex" at the end doesn't matter. I can leave it out with identical results.
The blank space at the beginning of SuffixPattern doesn't matter either. I can leave it out with identical results.

<appender name="IDP_SYSLOG" class="ch.qos.logback.classic.net.SyslogAppender">
    <SyslogHost>localhost</SyslogHost>
    <Port>514</Port>
    <Facility>AUTH</Facility>
    <SuffixPattern> [%logger:%level]  %msg %mdc{idpSessionId} from %mdc{clientIP}%nopex</SuffixPattern>
</appender>



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira