This should be fixed now with LOG4J2-905 and the %msg{nolookups} option.
Gary
On Thu, Aug 18, 2016 at 9:12 AM, Matt Sicker <boa...@gmail.com> wrote:
> Whoops, replied on the camel post.
>
> https://issues.apache.org/jira/browse/LOG4J2-905
>
> This issue looks relevant.
>
> On 18 August 2016 at 10:59, Luca Burgazzoli <lburgazz...@gmail.com> wrote:
>
> > Hello,
> > we have migrated apache camel to log4j2 and we have an issue when
> > logging stuffs with log4j2 as there is a clash between camel and
> > log4j2 syntax:
> >
> > As example, a user define a camel route that contains something like
> >
> > fileName=${date:now:yyyyMMdd-HHmmss}ID.${id}.gz"
> >
> > Then if log level is set do debug, camel tries to log such
> > configuration but then log4j2 kicks-in and tries to replace the
> > ${date:...} but it shouldn't as we really want to log the raw data.
> >
> > Is there any way to disable lookups in logging message ?
> >
> > Here a full story:
> > http://stackoverflow.com/questions/27103400/log4j2-how-
> > to-disable-date-lookup-log4j-throws-exception
> >
> >
> > Best regards,
> > Luca
> >
> >
> > ---
> > Luca Burgazzoli
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
> > For additional commands, e-mail: log4j-user-h...@logging.apache.org
> >
> >
>
>
> --
> Matt Sicker <boa...@gmail.com>
>
--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
