Hi,
Issue fixed. The problem was in the disruptor library, which we also migrated
from 3.4.4 to 4.0.0. Downgrading again to 3.4.4. fixed the problem.
Regards,
Joan.
-Original Message-
From: Piotr P. Karwasz
Sent: Thursday, January 25, 2024 1:20 PM
To: Log4J Users List
Subject: Re:
Hello,
I have checked the debug log using '-Dlog4j2.contextSelector' (that does not
log) with the debug log without using this variable.
I can't see any differences, except obviously the messages regarding async
contexts:
Async:
TRACE StatusLogger [AsyncContext@4857245] AsyncLoggerDisruptor
Hello,
Here is the trace when starting tomcat with
'-Dlog4j2.contextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector':
https://gist.github.com/joanbalaguero/1fa286417bfc9dbd3ce75e043bd26f3d
It seems the async contexts are started, but maybe someone can see something
Hi Ganesh,
I already have this
2.22.1. The war file
contains the right libraries, all in version 2.22.1.
Where can I see the supported tomcat/java versions depending on the log4j
version?
Thanks,
Joan.
-Original Message-
From: Ganesh S
Sent: Thursday, January 25, 2024 1:14 PM
Hi Piotr,
I already did it ... no success.
Thanks,
Joan.
-Original Message-
From: Piotr P. Karwasz
Sent: Thursday, January 25, 2024 1:20 PM
To: Log4J Users List
Subject: Re: Async logger not logging after upgrading tomcat, jdk and log4j
Hi Joan,
On Thu, 25 Jan 2024 at 12:06,
Hello,
I would like to ask about this issue before starting to post debug logs.
My application has been using async logging for years by setting this env
variable on tomcat 8.5.x running on java 11 with log4j-2.15/6/7/8/9:
