Log4j2 not working with tomcat and JULI #2092
-
|
I have a web application(WAR file) which is using log4j2 configuration. My My tomcat 9.0.36 is configured to use default java logger with default configuration. I don't want to replace log4j2 as default logger in tomcat. Let tomcat use JULI only. I just want the log4j in web application(war) to create a log file at Tomcat JULI config - |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 20 replies
-
|
Don't use relative paths like Try using |
Beta Was this translation helpful? Give feedback.
-
|
Is there a way to see more logs from StatusLogger by setting it to ALL/Trace @ppkarwasz ? |
Beta Was this translation helpful? Give feedback.
-
|
The |
Beta Was this translation helpful? Give feedback.
-
|
@ppkarwasz okay then this is all I have. Any idea what is going wrong? While debugging it is still pointing to Default appender/logger. |
Beta Was this translation helpful? Give feedback.
-
|
Finally this worked. Something is wrong with URI is also not coming as null and giving the proper path of file |
Beta Was this translation helpful? Give feedback.
-
|
I tested on my local (vanilla) Tomcat 9.0.53 and except problems in your configuration (it's a mix of Log4j 1.x and 2.x configuration properties) I could not reproduce your detection problem. The configuration I used is: <Configuration xmlns="http://logging.apache.org/log4j/2.0/config">
<Appenders>
<Console name="console">
<PatternLayout pattern="%d{yyyy-MM-dd HH:mm:ss} %-5p %c{1}:%L [%M] - %m%n"/>
</Console>
<RollingFile name="file"
filePattern="${sys:catalina.base}/logs/application-%d{yyyy-MM-dd}.log"
fileName="${sys:catalina.base}/logs/application.log">
<PatternLayout pattern="%d{yyyy-MM-dd HH:mm:ss} %-5p %c{1}:%L [%M] - %m%n"/>
<SizeBasedTriggeringPolicy size="10MB"/>
<DefaultRolloverStrategy max="10" fileIndex="min"/>
</RollingFile>
</Appenders>
<Loggers>
<Root level="WARN">
<AppenderRef ref="console"/>
<AppenderRef ref="file"/>
</Root>
</Loggers>
</Configuration>I would really advise against configuring the logging backend: it can cause problems during upgrades of Log4j Core. You should at least add a guard to your cast to final URL location = getClass().getResource("/log4j2.properties");
final org.apache.logging.log4j.spi.LoggerContext ctx = LogManager.getContext(false);
if (ctx instanceof LoggerContext) {
((LoggerContext) ctx).setConfigLocation(location.toURI());
} |
Beta Was this translation helpful? Give feedback.
-
|
I just tried to use XML and it worked!! Still dont know why it was not working with properties file. Will be removing the use of LoggerContext. One question @ppkarwasz what is the best way to append to a single file by mutliple threads using my customLogger which uses log4j2 internally. I noticed making loggers async is faster than having async appenders to a file - https://logging.apache.org/log4j/log4j-2.2/manual/async.html#:~:text=(Async%20Appenders%20use%20ArrayBlockingQueue%20internally,alternative%20to%20Buffered%20File%20Appenders. |
Beta Was this translation helpful? Give feedback.
-
|
Async loggers are faster than async appenders, since they perform most of the work (formatting) on the calling thread. The whole process can also be garbage free. If you use a custom logging API, the performance will be slightly slower (more method calls) and your implementation can introduce temporary objects (e.g. if you have vararg) methods. I would strongly recommend to use the Log4j API directly (e.g. test the OpenRewrite recipe I contributed). With a custom logger (even if it is hardcoded to an established API) you lose a lot of tools written for that API: Error Prone rules, rewrite recipes, etc. |
Beta Was this translation helpful? Give feedback.
-
|
@ppkarwasz This config is not printing all logs to file. Its only printing error level logs. |
Beta Was this translation helpful? Give feedback.
-
|
Remark: I maintain a small set of classes that improve the support of Log4j API and Log4j Core in Tomcat (cf. copernik-eu/log4j-plugins). The main problem with Log4j API + Tomcat is that Tomcat has a very primitive classloader configuration. If a webapp comes with I have used |
Beta Was this translation helpful? Give feedback.
Finally this worked. Something is wrong with
LoggerContextso I had to set it manually.URI is also not coming as null and giving the proper path of file