Hola,
Ok, this particular one is not 100% FUD, it's merely hugely inflating issues which may occur when log4j is used and is deployed in certain ways, and which can also be caused by bugs in Tomcat's logging usage (getting a logger without the proper classloader being bound, etc). In the end, having a more robust logging implementation would most likely also avoid problems.
Agreed. Do we want to do something in this area beyond the current JULI implementation for Tomcat 6.0? Yoav --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
