[logback-dev] [JIRA] Resolved: (LBCORE-180) conversion word followed by a non-conversion word caues an exception

[Ceki Gulcu (JIRA)]

     [ http://jira.qos.ch/browse/LBCORE-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ceki Gulcu resolved LBCORE-180.
-------------------------------

    Fix Version/s: 0.9.26
       Resolution: Fixed

I added an explanation in relation to this bug. See "Restrictions on literals immediately following conversion words"  in http://logback.qos.ch/manual/layouts.html 
 

> conversion word followed by a non-conversion word caues an exception
> --------------------------------------------------------------------
>
>                 Key: LBCORE-180
>                 URL: http://jira.qos.ch/browse/LBCORE-180
>             Project: logback-core
>          Issue Type: Bug
>          Components: Pattern
>    Affects Versions: 0.9.26
>            Reporter: Michael Osipov
>            Assignee: Ceki Gulcu
>            Priority: Critical
>             Fix For: 0.9.26
>
>
> I have defined the following pattern:
> <Pattern>Zeitstempel: %date%nKontext: %contextName%nAngeforderte URI: %X{req.requestURI}%nQueryString: %X{req.queryString}%nNachricht: %msg</Pattern>
> It is intended for a SMTPAppender. The outcome is:
> Zeitstempel: 2010-11-08 12:49:54,241%PARSER_ERROR_nKontext: michael%PARSER_ERROR_nAngeforderte URI: /michael/start%PARSER_ERROR_nQueryString: %PARSER_ERROR_nNachricht: Login::  ms....
> The workaround is either enclose the %n in %() or put a space between. Anyway, this should be fixed or noted in the docs.

-- 
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