Tomcat 10 log4j2 configuration ignored in IntelliJ IDEA on Windows

Problem

When running a web application on Tomcat 10 from IntelliJ IDEA on a Windows system, the log4j2 configuration specified in Tomcat's setenv.bat or logging.properties (using -Dlog4j.configurationFile) might be ignored.

This can lead to:

• Errors during startup like Could not load Logmanager "org.apache.logging.log4j.jul.LogManager".
• Errors like ERROR StatusLogger Reconfiguration failed: No configuration found for '...' at 'null' in 'null'.
• Application logs using the default Tomcat JULI logging format instead of the patterns defined in log4j2-tomcat.xml.
• Tomcat itself might partially use the configuration (e.g., creating log files), but the deployed web application fails to find or apply it.

The issue occurs even if the CLASSPATH and CATALINA_OPTS seem correctly set and displayed in the IntelliJ IDEA console during startup, and even if Tomcat works correctly when started from the command line outside the IDE.

Cause

The problem often stems from the format of the file path provided to the -Dlog4j.configurationFile Java system property when running Tomcat via IntelliJ IDEA on Windows. The standard Windows path format (e.g., D:\path\to\config.xml) or even variations like file:D:/path/to/config.xml might not be correctly interpreted as a valid file URI by the Java Virtual Machine launched by the IDE in this specific context.

Resolution

To ensure IntelliJ IDEA and the underlying Java process correctly locate the log4j2 configuration file on Windows, specify the path using the file:/// URI scheme.

1. Modify setenv.bat: If you define the configuration file path in %CATALINA_HOME%\bin\setenv.bat, update the CATALINA_OPTS line:

   rem Use forward slashes and the file:/// prefix
   set CATALINA_OPTS=%CATALINA_OPTS% -Dlog4j.configurationFile=file:///D:/path/to/your/tomcat/log4j2/conf/log4j2-tomcat.xml
   
   rem Also ensure the LogManager is set if needed
   set CATALINA_OPTS=%CATALINA_OPTS% -Djava.util.logging.manager=org.apache.logging.log4j.jul.LogManager
   

   Replace D:/path/to/your/tomcat/ with the correct absolute path to your Tomcat installation directory, ensuring you use forward slashes (/).

2. Update IntelliJ IDEA Run Configuration: If you are setting VM options directly in the Tomcat Run/Debug configuration within IntelliJ IDEA, apply the same format there:

   • Go to Run -> Edit Configurations...
   • Select your Tomcat Server configuration.
   • Navigate to the Server tab.
   • In the VM options field, add or modify the property: -Dlog4j.configurationFile=file:///D:/path/to/your/tomcat/log4j2/conf/log4j2-tomcat.xml
   • Ensure the -Djava.util.logging.manager=org.apache.logging.log4j.jul.LogManager property is also present if required for your setup.

Using the file:/// prefix followed by the absolute path with forward slashes ensures the path is correctly interpreted as a file URI by the JVM when launched from IntelliJ IDEA on Windows, allowing log4j2 to find its configuration file.