DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33143>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33143 ------- Additional Comments From [EMAIL PROTECTED] 2005-01-21 03:46 ------- Thanks for your interest in this. I'm not sure if I made the problem clear, however. I'm not asking for Tomcat to change the way its own logging works or anything like that. I'm not asking for Tomcat to provide better handlers for the JDK logging system. The problem I'm trying to solve is this. If you have two webapps that both use JDK logging internally, then they both share the same set of Logger instances. This means that if they use the same names for the loggers (which would be the case if they both make use of the same support library, for example) then their log messages get mixed up together. The log messages from the second webapp will be sent to the handlers of the first webapp and vice versa. Note that the code actually doing the logging is probably not even aware that it's running inside a container. This is arguably a (minor) security issue as well, as a rogue webapp can grab references to the loggers used by other webapps and screw with them. Using this replacement LogManager does nothing more than isolate Loggers to the servlet context that creates them, rather than having them global to the entire VM which is the default. It's still up to the webapp to provide appropriate log filters and handlers for what it wants to do. The reason for my request is that, due to the design of the JDK logging system, this can only be addressed by the container. Without this, there's nothing a correctly written webapp can do to prevent other webapps sending their messages to its logs (accidently or otherwise). Now, you can legitamately argue that JDK logging is badly designed and you don't see why Tomcat should have to fix its mistakes. Fair enough. But at the end of the day, correctly written webapps that happen to use JDK logging may not work too well when they're run inside Tomcat. I think my biggest obstacle to getting this in is that 99.9999% of webapps running inside Tomcat use Log4j. I think I'm the only person in the world who needs this :-) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
