Hi Piotr,
Thanks for your explanation.
Indeed, once I hard code the path to the log4j configuration file into web.xml,
logging works in both cases (app undeployment/deployment as well as Tomcat
shutdown/restart).
However, what I was trying to achieve by using a servlet context listener was
Hello Log4j Team,
One of the great new features of Log4j2 is the lambda lazy logging.
Since we migrated to Log4j2 we have liberally been trying to take advantage of
this where we can.
In the last few releases though, in preparation for Log4j 3.x the Log4j
Supplier has been deprecated without
