Robert Taylor wrote the following on 8/3/2005 7:06 PM:
Rick, I'm sure you already have, but just in case you haven't...
http://jakarta.apache.org/tomcat/tomcat-5.5-doc/logging.html
It provides a pretty detailed explaination of how to configure
cross-context logging using either log4j or java.util.logging package.
BTW, Tomcat 5.5 uses Commons Logging which I think defaults to
java.util.logging if its found and no other logging configs are specified.
Yea that was the problem. Thanks Robert. I actually didn't bother to
read those docs because I was assuming a default cross-context log would
be provided. Although I'm still a bit confused since I never ran into a
stdout log that Tomcat 5.5 says it should produce for stack traces?
(Unless by stdout log they mean the stdout to the console?):
"Tomcat 5.5 has done away with localhost_log which you may be familiar
with as the runtime exception/stack trace log. These types of error are
usually thrown by uncaught exceptions, but are still valuable to the
developer. They can now be found in the stdout log."
Not a big deal though since I'm back to using 5.0 because they changed
the way the JNDI stuff is done in tomcat 5.5 and since I'm deploying
eventually to tomcat 5 and not 5.5, I just went back to 5.0 locally as well.
--
Rick
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
