Thank you for the info. Removing the -D property from our launch script
and using and seems to have fixed the problem!
This will work for us :-)
THANK YOU!!!
~ Joe ~
On Fri, May 11, 2018 at 8:38 PM Carter Kozak wrote:
> I think this issue is tracked here:
>
I think this issue is tracked here:
https://issues.apache.org/jira/browse/LOG4J2-2312
On Fri, May 11, 2018 at 9:12 PM, Franz Wong wrote:
> I also got the same issue when I used AsyncLoggerContextSelector. But if I
> use the default selector, but changing the logger to and
>
I also got the same issue when I used AsyncLoggerContextSelector. But if I
use the default selector, but changing the logger to and
, then the log generated is fine.
-Franz
On Sat, May 12, 2018 at 9:09 AM, Joseph Husby wrote:
> Hello!
>
> We are trying to run log4j 2.11.0
Hello!
We are trying to run log4j 2.11.0 with a JSONLayout and async appender. We
have set the JSONLayout properties="true" but are not getting the json
properties. Without the async appender, we DO get the json properties.
With the default synchronous appender, the logs looks like this:
, {
Hello,
I'm currently migrating our codebase to Log4j2 (2.9.1) in a Tomcat 9.0.7
environment, and while testing different configurations I noticed a weird,
what i think also undocumented, difference between the standard usage and
when starting with -DLog4jContextSelector=org.apa