Hello,
Check the dependency hierarchy, which version of log4j is being used.
I had faced similar issue, even though if I specified some particular
version of log4j, maven was not picking that particular version though
there were no other dependencies which were using log4j at any nested level.
For that I had added the below in the pom.xml file
<properties>
<log4j2.version>2.22.1</log4j2.version></properties>
After this also if it doesn't work pick the appropriate version of log4j
which supports your version of Java and tomcat.
On Thu, Jan 25, 2024, 4:35 PM <joan.balagu...@ventusproxy.com> wrote:
> 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:
>
> -DLog4jContextSelector=org.apache.logging.log4j.core.async.BasicAsyncLoggerContextSelector
>
> Now we have migrated to Tomcat 10.1.18, java 17 and log4j-2.22.1. With the
> above variable set, nothing is logged. If I remove it then it starts to log
> again, but without async.
>
> Is there any change I'm missing regarding this async logging when moving
> to these new versions of tomcat, java and log4j?
>
> Thanks,
>
> Joan.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
> For additional commands, e-mail: log4j-user-h...@logging.apache.org
>
>
