[ 
https://issues.apache.org/jira/browse/LOG4J2-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ralph Goers resolved LOG4J2-136.
--------------------------------

    Resolution: Fixed
      Assignee: Ralph Goers

I applied your patch with a modification in revision 1426803. The change I made 
was to allow a Throwable converter pattern to be specified. If one is there it 
will be used to format the Throwable.  Thanks for the patch. 

Please verifiy and close.
                
> Syslog: Optional escaping of newlines in message body, optionally include 
> stack trace
> -------------------------------------------------------------------------------------
>
>                 Key: LOG4J2-136
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-136
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Appenders, Layouts
>    Affects Versions: 2.0-beta3
>         Environment: N/A
>            Reporter: Scott Severtson
>            Assignee: Ralph Goers
>            Priority: Minor
>              Labels: patch
>             Fix For: 2.0-beta4
>
>         Attachments: syslog-escape-newlines-and-include-stack-trace.patch, 
> syslog-escape-newlines.patch
>
>
> Syslog (both RFC-3164 and 5424) use newline characters to frame messages. As 
> Log4J2 messages may include newlines in the message body, it is necessary to 
> replace newlines with a configurable escape string.
> I've implemented a configuration option "newLineEscape" which accepts a 
> replacement string. The default is to not escape newlines (i.e. current 
> behavior).
> I've also implemented a configuration option "exceptionConverstion", which 
> accepts the same options as PatternLayout's %exception field. If no value is 
> specified, exceptions are not included.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to