Trying log4j3 with java24 (virtual threads)

<[email protected]> Sat, 25 Jan 2025 13:37:27 +0100
Newsgroups gmane.comp.jakarta.log4j.user
Message-ID <[email protected]>
Hello,

I want to try log4j3 ... and I have some questions before getting =
started. We are in the process to migrate to virtual threads, our web =
application is running on java24/tomcat 10.1.34, still with log4j =
2.24.2.

1. Being log4j3 virtual thread compatible, must I use sync loggers =
instead of the async ones?

2. My current maven looks like below now, where log4j2.version is =
'2.24.2'

    <!-- disruptor -->
    <dependency>
      <groupId>com.lmax</groupId>
      <artifactId>disruptor</artifactId>
      <version>4.0.0</version>
    </dependency>

    <!-- log4j -->
    <dependency>
      <groupId>org.apache.logging.log4j</groupId>
      <artifactId>log4j-core</artifactId>
      <version>${log4j2.version}</version>
    </dependency>
    <dependency>
      <groupId>org.apache.logging.log4j</groupId>
      <artifactId>log4j-api</artifactId>
      <version>${log4j2.version}</version>
    </dependency>
    <dependency>
      <groupId>org.apache.logging.log4j</groupId>
      <artifactId>log4j-jakarta-web</artifactId>
      <version>${log4j2.version}</version>
    </dependency>
    <dependency>
      <groupId>org.apache.logging.log4j</groupId>
      <artifactId>log4j-slf4j-impl</artifactId>
      <version>${log4j2.version}</version>
    </dependency>
    <dependency>
      <groupId>org.apache.logging.log4j</groupId>
      <artifactId>log4j-1.2-api</artifactId>
      <version>${log4j2.version}</version>
    </dependency>
=09
=09
   With log4j3, do I still need all these dependencies? I suppose I can =
remove disruptor if I use sync loggers, but is there anything else not =
necessary to run my web application now?
  =20
   For example, I see 'log4j-jakarta-web' still in '3.0.0-alpha1' since =
Jun 21, 2023.
  =20
  =20
Thanks,

Joan.