tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chen Levy <>
Subject RE: Tomcat 8.5.4 and Log4j2
Date Fri, 29 Jul 2016 01:16:29 GMT
From: Mark Thomas
Sent: Thursday, July 28, 2016 15:32
To: Tomcat Users List
Subject: Re: Tomcat 8.5.4 and Log4j2

On 28/07/2016 20:09, Chen Levy wrote:
> Hello all
> I’ve been using Tomcat 8.0.X with Log4j2, both for Tomcat logging and for my applicative
logs, for a long time now.
> It was done using the following jars:
> extras/tomcat-juli.jar
> extras/tomcat-juli-adapters.jar jars
> I’m in the process of upgrading to Tomcat 8.5.4 and according to
these jars are no longer distributed.
> I followed the instructions in
and performed the following:
> 1. Added  -Djava.util.logging.manager=org.apache.logging.log4j.jul.LogManager  to the
java command
> 2. Added  log4j-jul-2.6.2.jar  to the classpath
> Other than adding these through setenv.bat, I did not modify anything with the distribution
> Now, when invoking startup.bat, Tomcat starts and exits immediately, without any console
or log output

catalina.bat run

to start and report the error message.


To unsubscribe, e-mail:
For additional commands, e-mail:

Thanks for the hint Mark
There was a ClassNotFoundException where log4j-juli required log4j-api in the classpath, then
log4-core and finally disruptor.jar
So I moved these jars from Tomcat’s /lib folder, where I used to place them in v8.0, to
/bin folder, next to tomcat-juli.jar; and added them all to the classpath.

I’m no sure if that is the right way, but it’s working. I’m pasting the content of my
setenv.bat for those who may encounter this issue in the future (I’m using a file
as well if anyone is interested):

rem Set the classpath for Log4j2
set "CLASSPATH=%CLASSPATH%;%CATALINA_HOME%\bin\log4j-jul-2.6.2.jar;%CATALINA_HOME%\bin\log4j-api-2.6.2.jar;%CATALINA_HOME%\bin\log4j-core-2.6.2.jar;%CATALINA_HOME%\bin\disruptor-3.3.4.jar"

rem Log4j2 configuration
set CATALINA_OPTS=%CATALINA_OPTS% -Djava.util.logging.manager=org.apache.logging.log4j.jul.LogManager

Please let me know if there’s another, better way to do it

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message