Currently Tomcat has its own logging and Log4j only initialises when the webapp starts up. This makes it hard to track issues especially in our k8s environments.
This task is to setup tomcat to use log4j2 for its logging and to use the same single context for the webapp allowing for a single log4j config file to handle the whole running of the application.
There is an existing proof of concept but it was causing some tests to fail. We need to merge in these changes into the core
Currently Tomcat has its own logging and Log4j only initialises when the webapp starts up. This makes it hard to track issues especially in our k8s environments.
This task is to setup tomcat to use log4j2 for its logging and to use the same single context for the webapp allowing for a single log4j config file to handle the whole running of the application.
There is an existing proof of concept but it was causing some tests to fail. We need to merge in these changes into the core
https://github.com/dotCMS/core/pull/23964