a few users have complained that the instructions on tomcat 5.5's new logging page does not produce the log files. i have tested this and they are correct. the problem is not the configuration properties but that the instructions only mention the requirement of placing log4j.jar in common/lib when in fact commons-logging.jar in common/lib is *also* required. i have tested this on a fresh 5.5.5 a moment ago by copying the configuration on the logging page, and just adding commons-logging and this resolves this problem. i am also interested if perhaps a tomcat dev could explain why a log4j configuration will not work on tomcat startup unless commons-logging is also in common/lib.
Created attachment 13647 [details] adds note to acquire commons-logging, modifies some other parts lightly to prevent further complaints, is there any way we can patch the website file easily soon?
Actually, and this is more accurate, what you would need in the commons-logging wrapper for the logging implementation you're using (commons-logging.jar has the log4j wrapper). As for the startup thing, it's likely caused by the context classloader which is bound.
(In reply to comment #2) > in in -> is
OK, patch applied (slightly modified), in time for 5.5.6.