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 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 Burgazz
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 wrote:
> Hello,
> we have migrated apache camel to log4j2 and we have an issue when
> logging stuffs with log4j2 as there is a clash betwee
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:MMdd-HHmmss}ID.${id}.gz"
Then if log level is
