Hi!
I still do not know what is causing this behavior, but I found a workaround in case anyone else stumbles upon this problem:
In my log4j.properties I left the log4j.rootCategory property alone and only set log4j.category.package.name.of.my.classes properties for each package in my webapp to DEBUG.
This way I only get the DEBUG output of my own classes and not ALL debug messages generated by the container.
I still wonder why my log4j.properties in /WEB-INF/classes should reconfigure the container's whole logging mechanism. Either this is a major bug or tomcat4's doing it right was one.
I will look into the issue. However, if it's a bug, then not much may be done about it, and likely the fix will need to be in c-l (Tomcat 4 integration of c-l is unreliable).
As Jacob mentioned, you will need both c-l and log4j in /WEB-INF/lib (both the logger and the c-l logger wrapper should reside in the classloader where they are used). Note that this caused big problems in TC 4.1.x, so maybe you didn't do that.
-- xxxxxxxxxxxxxxxxxxxxxxxxxxxxx R�my Maucherat Senior Developer & Consultant JBoss Group (Europe) S�RL xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
