On Sat, Apr 4, 2009 at 9:08 PM, Caldarale, Charles R <chuck.caldar...@unisys.com> wrote:
> I think I figured out what's going on. Tomcat 5.5 uses an unmodified > LogFactory from commons-logging, which pokes around for logging mechanisms - > and finds your log4j.jar inside your webapp. Tomcat 6.0, on the other hand, > uses a modified LogFactory, which is hard-coded to use an enhanced version of > java.util.logging, so it never looks for your log4j. Looks like Tomcat 6 > implements what you're looking for, so you might want to consider moving up. I just confirmed this behavior on Tomcat 6.0.18 - my production apps work the way I expected - I always get a stack trace when I break the app, and it never gets re-routed to my apps webapp. Your explanation makes sense. I'll update the bug I reopened. I've been needing a good reason to upgrade to 6 anyway, now I have one :) >> I'm also still looking into a (possibly?) related issue >> that I have where log4j in every webapp deployed beyond >> the first fails to auto-configure. Unfortunately, I still have something fishy going on here, even in Tomcat 6.0.18. It is different than it was under 5.5, but still undesirable. Now, log4j doesn't self configure for any of my webapps. But strangely, only two of them print log4j:WARN messages about log4j not being configured, while under Tomcat 5.5, all of my apps after the first printed that message. I'll have to do some more investigation there... but I may put that on hold until after I finish merging tomcat 6 into our official build process. Thanks, Dan --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
